codev

codev MCP gives AI agents a secure, live view of the Salesforce projects your team manages in codev. Connect Claude, Codex, GitHub Copilot, or any client that supports MCP over Streamable HTTP to understand delivery state, investigate failures, and act with the same permissions you have in codev.

What your agent can do

With codev MCP, an agent can:

• Discover Salesforce projects and their repository configuration.
• Follow builds, release candidates, releases, and what is deployed or pending in each environment.
• Inspect pull-request validations, deployment and test results, code analysis, compliance findings, and review status.
• Read connected work items from Jira, Azure DevOps, or GitHub.
• Explore registered environments, Salesforce orgs, pool capacity, assignments, and review environments.
• Query delivery performance insights for a project.
• Fetch, extend, and release a pool environment for the signed-in user.

Most capabilities are read-only. The pool environment actions are the state-changing operations, and interactive users can manage only their own assignments.

Connect

Every codev instance exposes an MCP endpoint at:

https://<your-tenant>.flxbl.io/sfp/api/mcp

Replace <your-tenant> with your codev tenant subdomain. Do not put credentials in the client configuration: interactive clients discover codev's OAuth 2.1 authorization server and open browser sign-in when they first connect.

Claude Code

claude mcp add --transport http codev https://<your-tenant>.flxbl.io/sfp/api/mcp

Run /mcp in Claude Code and select codev to complete sign-in.

Codex

codex mcp add codev --url https://<your-tenant>.flxbl.io/sfp/api/mcp
codex mcp login codev

Cursor

Install codev from the Cursor Marketplace and enter your codev tenant subdomain when prompted. For example, if your codev URL is https://acme.flxbl.io, enter acme.

Cursor then connects to the tenant's MCP endpoint and opens codev sign-in through OAuth when authentication is required. The marketplace configuration never stores a password or access token.

GitHub Copilot and other clients

Use this generic MCP configuration:

{
  "mcpServers": {
    "codev": {
      "type": "http",
      "url": "https://<your-tenant>.flxbl.io/sfp/api/mcp"
    }
  }
}

In VS Code with GitHub Copilot, place the configuration in .vscode/mcp.json. Claude Desktop and claude.ai users can add the URL as a custom connector.

To verify the connection, ask your agent:

List the available pools.

Authentication and identity

Interactive connections use OAuth 2.1. Each tool call runs with the signed-in user's codev role, and pool checkouts are attributed to that user's email.

CI jobs and scripted agents can use a codev application token in an Authorization: Bearer header. Application tokens are intended for controlled automation and can act independently of an individual user, so store them in a secret manager and grant access carefully.

Registry and implementation

This repository is the public home for codev's MCP registry metadata and connection documentation. The remote MCP implementation is delivered as part of codev; it is not duplicated in this repository and remains governed by the codev product licence.

The registry definition is maintained in server.json and published to the official MCP Registry for standards-based discovery. Downstream catalogs, including GitHub's public MCP Registry, decide independently when and which entries to index.

Documentation and support

• Connect an agent to codev
• Complete MCP tools and actions reference
• codev product overview
• Report a documentation or connection issue

For a security concern, follow the private reporting process in SECURITY.md.