Connect your AI MCP to Serpent

Connection details

Point your MCP client at https://mcp.serpent.cloud/mcp over streamable HTTP. Authentication is OAuth 2.1 with PKCE on scope serpent:mcp, so your client opens a browser to consent and no API key sits in the config.

Client configuration

{
  "mcpServers": {
    "serpent": {
      "type": "http",
      "url": "https://mcp.serpent.cloud/mcp"
    }
  }
}

That is the Claude Code and Cursor shape. Supported clients today include Claude, Cursor, Cline, Codex, Windsurf, and GitHub Copilot; each client's integration page carries its own snippet.

What you can run

Every tool is prefixed serpent_. A few of the ones you will reach for most:

• Deploy and pipelines - serpent_plan_deploy, serpent_execute_deploy_plan, serpent_trigger_pipeline, serpent_cancel_pipeline.
• Source control - serpent_create_pull_request, serpent_merge_pull_request, serpent_get_pull_request_checks_summary.
• Conflicts - serpent_detect_metadata_conflict and serpent_resolve_metadata_conflict.
• Context and orgs - serpent_get_workspace_context, serpent_resolve_target_org, serpent_create_scratch_org, and more.

Every MCP-triggered action still runs through Serpent's preflight checks, AI review, and mandatory human approval. MCP access is included on the free Essentials tier.