Log inSubmit server
Codev logo

Codev

Connects AI agents to live Salesforce delivery data, project status, validations, environments, and pool actions.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Codev

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://docs.flxbl.io/flxbl/sfp/api-reference/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

Salesforce project delivery context is exposed through the codev MCP server for agents that support Streamable HTTP. It can inspect projects, repositories, builds, releases, validations, deployments, tests, environments, connected work items, and delivery insights. Signed-in users can also fetch, extend, or release their own pool environments, while most other capabilities are read-only. Reach for it when an agent needs current codev delivery state or controlled Salesforce release operations.

Use cases

  • Inspect Salesforce release and deployment status
  • Investigate failed validations and test results
  • Review project delivery performance
  • Check pool capacity and environment assignments
  • Release a pool environment for the signed-in user

Key features

  • Salesforce project and repository discovery
  • Build, release, and deployment tracking
  • Validation, test, analysis, and compliance inspection
  • Jira, Azure DevOps, and GitHub work item access
  • Environment and pool management
  • OAuth 2.1 and application-token authentication

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

5/5 checks healthy over the last 35d

How Codev works

What codev does

The codev MCP server gives AI agents access to live delivery information for Salesforce projects managed in codev. It provides project and repository configuration, build and release progress, deployment state by environment, and the status of release candidates. Agents can also inspect pull-request validations, test and deployment results, code analysis, compliance findings, and review status.

Delivery context can include work items from connected Jira, Azure DevOps, or GitHub systems. The service also exposes registered environments, Salesforce orgs, pool capacity, assignments, and review environments. Project-level delivery performance insights are available for investigation and reporting.

How it works

Each codev tenant exposes a remote MCP endpoint at https://<your-tenant>.flxbl.io/sfp/api/mcp. MCP clients connect to that URL over Streamable HTTP. Interactive clients discover the tenant’s OAuth 2.1 authorization server and open a browser sign-in flow, so credentials should not be placed in client configuration.

Tool calls use the signed-in user’s codev role. Pool checkouts are associated with that user’s email. Controlled automation can instead send a codev application token in an Authorization: Bearer header. Application tokens operate independently of a specific interactive user and should be stored in a secret manager.

Setup and configuration

Replace <your-tenant> with the tenant subdomain in the MCP endpoint. Claude Code can be configured with claude mcp add --transport http codev <URL>, followed by sign-in through /mcp. Codex uses codex mcp add codev --url <URL> and codex mcp login codev.

Cursor users can install codev from the Cursor Marketplace and provide the tenant subdomain when prompted. Other HTTP-capable clients can use an MCP configuration containing the endpoint URL and no embedded credentials. In VS Code with GitHub Copilot, that configuration belongs in .vscode/mcp.json; Claude Desktop and claude.ai can add the URL as a custom connector.

Tools and capabilities

The codev MCP server supports agents that need to:

  • Discover Salesforce projects and repository settings.
  • Track builds, release candidates, releases, and environment deployment state.
  • Review pull-request validation, deployment, test, analysis, compliance, and review results.
  • Read linked Jira, Azure DevOps, and GitHub work items.
  • Examine Salesforce orgs, environments, pool capacity, assignments, and review environments.
  • Query project delivery performance insights.
  • Fetch, extend, or release a pool environment for the signed-in user.

Limitations and notes

Most available operations do not change state. Pool environment fetch, extension, and release are the stated state-changing actions, and interactive users can manage only their own assignments. The remote MCP implementation is delivered with the codev product; this repository contains registry metadata and connection documentation rather than a duplicated implementation. Access remains subject to the permissions granted by the tenant and authenticated identity.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Codev

codev is an MCP server that connects AI agents to Salesforce project delivery data managed in codev. Its main tools discover projects, inspect builds, releases, validations, environments, work items, and delivery insights, while also allowing signed-in users to fetch, extend, or release their own pool environments. Authentication uses OAuth 2.1 or application tokens.

Configure your MCP client with your tenant endpoint: `https://<your-tenant>.flxbl.io/sfp/api/mcp`. Claude Code and Codex provide CLI commands for adding the URL, while other clients can use a standard Streamable HTTP configuration. Sign in through the OAuth browser flow when prompted.

Yes, codev works with Cursor through the Cursor Marketplace. Install codev, enter your codev tenant subdomain, and complete the OAuth sign-in flow when Cursor connects. The marketplace configuration does not store a password or access token.

Interactive agents authenticate with OAuth 2.1, and each call uses the signed-in user’s codev role. CI jobs and scripted agents can send a codev application token in an `Authorization: Bearer` header. Store application tokens in a secret manager and restrict their access.

Yes, authenticated users can fetch, extend, and release pool environments. These are the documented state-changing actions, and interactive users can manage only their own assignments. The server can also read pool capacity, assignments, registered environments, and review environments.

Related MCP servers

All in Customer Data Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCodev AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/codev?style=directory)](https://allmcps.com/mcp/codev)
HTML Embed
<a href="https://allmcps.com/mcp/codev"><img src="https://allmcps.com/api/badge/codev?style=directory" alt="Codev on AllMCPs" /></a>