Serpent + Cline for Salesforce DevOps
Serpent ships a native MCP server, so Cline's autonomous coding agent can plan, review, and trigger Salesforce deployments directly.
How to connect
Serpent is the only Salesforce DevOps platform with a native MCP server, and Cline adds it in cline_mcp_settings.json, which you open from VS Code with MCP Servers > Configure MCP Servers. It runs at https://mcp.serpent.cloud/mcp over streamable HTTP, with OAuth 2.1 sign-in.
{
"mcpServers": {
"serpent": {
"type": "streamableHttp",
"url": "https://mcp.serpent.cloud/mcp"
}
}
}- Serpent signs your client in with OAuth 2.1 on first connect, so no API key sits in your config file.
- Your client then discovers Serpent's four MCP tools automatically: plan_deploy, create_pull_request, resolve_metadata_conflict, and trigger_pipeline.
- Every MCP-triggered action still runs through Serpent's preflight checks and requires your human approval before anything ships.
One workflow: deploying from a Cline task
Give Cline a task like "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 session. See the full MCP tool list for what else your AI client can run.
Common questions
Start free. No credit card, no install, no commitment.
Set up in under 15 minutes. No DevOps hire needed.