codev
io.github.flxbl-ioPublished by GitHub account flxbl-iov1.0.1Updated Oct 24, 2026
Connect AI agents to codev for Salesforce projects, builds, releases, validations, and insights.
Overview
Connects an AI assistant to codev for live Salesforce project delivery context: builds, releases, validations, environments and insights.
- What you can do
- Discover Salesforce projects and their repository configuration
- Follow builds, release candidates, releases and what is deployed or pending per 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, and query delivery performance insights
- Fetch, extend and release a pool environment for the signed-in user
- When to use it
- Useful when an assistant should reason about a team's Salesforce delivery state: investigating failed validations or deployments, checking what is released or pending in an environment, or reviewing compliance and test results without leaving the chat.
- Requirements
- A remote MCP endpoint at the tenant's codev subdomain over Streamable HTTP; no package install. Interactive clients sign in through OAuth 2.1 in the browser. CI or scripted agents can instead use a codev application token in an Authorization Bearer header.
Installation
In SourceWeft
- Open codev in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Follow the launch instructions in the repository.
README
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:
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
Run /mcp in Claude Code and select codev to complete sign-in.
Codex
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:
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.
Source: README.md at commit 2abec49
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.