← Integrations
Serpent + GitHub Copilot for Salesforce DevOps
Serpent ships a native MCP server, so GitHub Copilot's agent mode can plan, review, and trigger Salesforce deployments directly.
In practice
How to connect
Serpent is the only Salesforce DevOps platform with a native MCP server. Connecting GitHub Copilot takes one config entry:
- Add Serpent's MCP server to GitHub Copilot's MCP configuration in VS Code with your Serpent API token.
- GitHub Copilot discovers Serpent's four MCP tools, plan_deploy, create_pull_request, resolve_metadata_conflict, and trigger_pipeline, automatically.
- Every MCP-triggered action still runs through Serpent's preflight checks and requires your human approval before anything ships.

One workflow: deploying from a Copilot Chat prompt
Ask GitHub Copilot to "scope a deployment for the new approval flow to UAT." Serpent's plan_deploy tool maps the exact components, you review the plan, and create_pull_request opens it for approval. Once approved, trigger_pipeline kicks off the deployment and reports status back in the same conversation. See the full MCP tool list for what else your AI client can run.
Common questions
Common questions
Can GitHub Copilot deploy to production without me?
No. Every MCP-triggered deployment still requires your human approval before it ships.
Do I need to install anything in my Salesforce org?
No. Point GitHub Copilot at Serpent's MCP server and you're connected.
Start free. No credit card, no install, no commitment.
Set up in under 15 minutes. No DevOps hire needed.
