One MCP server for every Salesforce admin and developer.
Admin, Developer, Architect, DevOps, RevOps — one Context Graph indexes your org so every role, on any AI agent, works from the same map. Seven tools read it today. Every one after inherits the graph.
One MCP, one Context Graph. Every role reads and plans against the same map.
Every object, field, flow, Apex class, validation rule and permission set, indexed with live structural dependencies. Clientell MCP gives your AI agent a structural map of your org, turning complex admin, dev and RevOps questions into grounded answers.
- Objects
- Fields
- Flows
- Validation rules
- Apex
- Profiles
- Permission sets
- Reports
Salesforce Admins
Draft complex flows from plain English, trace field dependencies across the entire org, and see what a change would break before you run it.5 / 6You run it.Salesforce Developers
Give Claude Code, or whichever MCP client you use, the org context it does not have. Trace a runtime error through every flow and field that touches it, and get metadata-grounded answers instead of guesses.2 / 6You run it.RevOps Teams
Trace what is actually driving a pipeline metric, and get a dedupe plan checked against every reference before you run it.2 / 6You run it.IT and Enterprise Architects
Audit permission set matrices, map impact before a deploy, and surface orphaned automations before they become a problem.2 / 6You run it.
It is not just a search tool. It is a living map of your Salesforce org, read from inside the AI tools your team already uses. Every role builds faster, debugs deeper, and knows before it acts.
Unified intelligence across Admins, Developers, RevOps, Architects and DevOps, powered by one hosted MCP server. IT here covers the architect and DevOps work counted on the cards.
You describe a change in plain English. A Flow that keeps failing, duplicate Accounts piling up, a report that should exist but does not. The agent plans it against your real org, and names what the change would break. You run what you approve.
How it works
Objects, fields, flows, Apex, validation rules, and permissions. One unified graph connects your entire Salesforce team to accurate org intelligence.
Complete Metadata Graph: Indexes your org structure including objects, fields, flows, Apex, validation rules, and permission sets. Kept synchronized so AI assistants never guess your schema.
Live Record Context: Queries record data on demand directly through your authenticated Salesforce CLI session. Your CRM data stays in your org and is never copied or stored.
Safety and Governance: The AI agent plans and verifies changes against org dependencies before you deploy. Every update runs under your own credentials with a complete audit trail.
A structural map of your org, not a copy of your data
The graph indexes objects, fields, flows, and permissions: never your customer record contents. This structural separation lets your AI tools query org architecture in milliseconds while your record data stays in Salesforce.
Ask about the data boundaryDescribe the task in plain English. The MCP handles the rest.
Describe what you need in plain English. The server reads the graph, resolves cross-object dependencies, and executes the workflow end to end with zero manual configuration.
Every result comes with the change plan drafted against your real metadata. You review the output and execute it through your own CLI.
Flow authoringAdmin · Developer
Draft a new Flow from plain language, or point at one that's failing and get the actual fix.
build_or_fix_salesforce_flowNames, identifiers and relationships. Not record contents.
The graph answers which: which flow touches which field, which profile reaches which object. What it does not store: customer record contents, Slack message bodies, Gmail message bodies, Jira issue contents. Those stay in their source systems.
Read-only, and the database enforces it
Not read-only by convention. Queries against your org’s graph run through the database’s read-only execution path, so a write cannot be issued even by mistake. The graph stays a faithful index of Salesforce architecture and nothing else.
MATCH (f:Field {name: "Custom_Segment__c"})
<-[:REFERENCES]-(x)
RETURN x.type, x.name
✓ 7 rows
No write path exists on this connection
It will never touch your org without you running it
A system that cannot deploy independently has no incentive to hallucinate confidence. The agent writes the change plan, and you run it as sf commands on your machine under your own credentials. Clientell holds a token to build the metadata index, but nothing that can read your customer records.
Proposed
Add Segment__c to the Enterprise Lead routing decision
sf project deploy start \
--source-dir force-app/main/default/flows \
--target-org production --dry-run
Salesforce ships its own MCP server. Keep it.
Salesforce’s official MCP server is the right tool for single-record operations. Clientell handles the org audits, pre-deployment blast radius checks, and schema reasoning no live API call can resolve. An MCP client runs both servers side by side without conflict.
Standard Actions
single-record CRUD & live SOQL
Deep Reasoning & Audit
org graph, audits, blast radius
Workspace Conflict
coexists side by side in client
| You ask | Salesforce Official MCP | Clientell Context Graph |
|---|---|---|
| Audit technical debt & orphaned metadata | No API exists. Requires manual Setup inspection across thousands of items. | Generates full org debt scores, orphaned automations, and unused field reports. |
| What breaks if I deploy this change? | No pre-deploy dependency check. Deploy failures happen at runtime. | Simulates deploy blast radius across Apex, Flows, and Profiles beforehand. |
| What breaks if I delete this field? | No API call returns this. Requires manual 'Where is this used?' clicks. | Traverses the complete dependency graph in milliseconds to identify all references. |
| Draft or debug a complex Flow | Can create simple records, but cannot author or trace Flow logic. | Drafts valid Flow XML and isolates failing steps with full schema context. |
| Safe duplicate merge plan | Standard merge without child record or foreign key safety validation. | Verifies all foreign key and master-detail references before drafting the merge plan. |
| Which profiles & permission sets can edit this? | Raw metadata read, but resolving effective user access requires manual calculation. | Instantly resolves effective field and object access across all permission sets. |
| Why was this custom rule created? | Out of scope. Salesforce stores current configuration, not decision history. | Traces origin rationale from linked Jira tickets, Slack threads, and Gmail discussions. |
| Create or update records directly | Yes. Direct write capability against the live org. | Drafts the plan for your review. You execute via your local sf CLI session. |
Both servers register under different namespaces and run side by side without interference.
Compared
What each MCP server actually does
Three hosted MCP servers for Salesforce, compared on what their own documentation says. Checked 18 August 2026. Where a competitor’s docs do not cover something, this says so rather than claiming they cannot do it.
| Capability | Context GraphClientell MCP | Salesforce Hosted MCPdeveloper.salesforce.com | Cirra AIcirra.ai docs |
|---|---|---|---|
| Live org-wide dependency graph | YesObjects, fields, Flows, Apex, validation rules, profiles and permission sets, plus the links between them. | Not documentedNo public documentation of one was found. | Not documentedNo public documentation of one was found. |
| Writes to your org | No, by designIt reads, plans and drafts. You run the change. | YesSeparately scoped SObject servers, including sobject-all for full create, read, update and delete. | YesDocumented create, update and delete on both records and metadata. |
| Impact before a change | YesTraces what references a field or Flow and names what the change would break. | Not documentedNo public documentation of one was found. | Not documentedNo public documentation of one was found. |
| How access runs | Your local sessionRemote Streamable HTTP context index. Live record queries run through your own authenticated local Salesforce CLI session. The graph stores structure, never record contents. | Salesforce's infrastructureRuns inside Salesforce's hosted infrastructure, under the authenticated user's own Salesforce permissions. | Vendor-hostedA vendor-hosted remote endpoint connected to Salesforce through OAuth. |
| Tools exposed | 7Counted from the registered tool surface, not estimated. | VariesSplit across several scoped servers, so a single number does not describe it. | Not publishedNo public tool count was found, so none is given here. |
| Client support | Any MCP clientBuilt and verified against Claude Code. The rest are untested by us. | Claude, ChatGPT, Cursor, PostmanOfficial docs list these as tested, using OAuth Authorization Code with PKCE. | Claude, ChatGPT, Cursor, VS Code, GeminiOfficial docs publish setup for Claude/Claude Code/Desktop, ChatGPT, Codex, VS Code, Cursor, Cline and Gemini Enterprise. |
Salesforce Hosted MCP from its overview and server reference. Cirra AI from its public documentation. Clientell’s tool count from its own registered tool surface. “Not documented” means the reviewed public docs did not establish it, not that the product cannot do it. Checked 18 August 2026.
For developers
Clientell MCP and the Salesforce DX MCP server
Different layers, and you can run both. DX MCP moves code between your project and an org. Clientell answers what that code is connected to before you move it. An MCP client can run both servers at once, which is the setup we would expect a developer to want.
Local, open source
Salesforce DX MCP
A build-and-ship toolchain, driven by the source in your project.
- Runs with npx against an org your Salesforce CLI is already authenticated to.
- More than 60 tools across the development lifecycle.
- Metadata retrieve and deploy, including Apex.
- SOQL, permission set assignment, Apex test runs.
- LWC creation and migration, DevOps Center, Code Analyzer.
Hosted, structural index
Context GraphClientell MCP
A map of the org as it actually is, read before anything moves.
- No source tree and no deploy step.
- Indexes objects, fields, Flows, Apex, rules and permissions.
- Answers what references this field, and what a change would break.
- Reads records live through your own CLI session.
- Plans and drafts. You run the change.
One thing to be clear about. No general record CRUD tool was found in the DX MCP repo, and no live dependency graph was documented there either. Both statements are about what the repo publishes, not about what the tool could be made to do.
What we can actually show you,
and where each number comes from.
- 86.5%
- mean graded score with the graph (110 questions, Opus-graded)
- 44.2%
- same model, same questions, no graph (the control)
- 86.0%
- graph + text hybrid — indexing prose added nothing
- 200+
- Salesforce orgs across Clientell's practice (not an MCP figure)
- 0
- changes to your org you did not run yourself
- 2000+
- Salesforce orgs across Clientell's practice
Watch where each one stops
Five recordings of Clientell AI, the agent that acts on the org. Each one reads the org first, names the fields it checked, and lays out a plan. Then it waits. Nothing changes until a person approves it in writing. MCP is the layer underneath that reading and that plan, and it stops at the same line every time.
- It checks firstScans the org and checks every field, picklist value and object exists before it proposes a single screen.
- You approve“The plan looks good go ahead and deploy it to my Sandbox.”
- Then it actsThe agent builds the Flow and ships it to a Sandbox.
Built for whoever owns the org
Admins, developers, architects, DevOps and RevOps all ask the same org different questions. They get paged when a flow breaks, and they are the ones who have to explain why it was there in the first place.
- SOLO ADMIN
- REVOPS LEADS
- SF ARCHITECT
- DEVOPS TEAMS
- ORG ARCHITECT
- SYSTEM ADMINS
- PARTNER TEAMS
- ENTERPRISE OPS
- SALESFORCE OPS
- SALESFORCE TEAMS
One admin holding a decade of customisation together, or a partner team walking into a client org they have never seen. Same problem: no one can tell you what depends on what.
Frequently asked
Everything you need to know about Clientell MCP
Straight answers on the graph, what it stores, and what is actually shipping.
Salesforce's hosted MCP server can read and write records through scoped SObject servers, and a beta Headless 360 server adds some configuration actions. Cirra AI is a write-capable action layer for records and metadata. Neither publishes a live dependency graph. Clientell indexes objects, fields, flows, Apex and validation rules, plus the links between them, and only drafts changes for you to run. That is what lets it name a break before you run the change.
No. The graph indexes names, IDs and relationships, never record contents. Record data is read live through your own authenticated Salesforce session, on your own machine.
The graph stores which component references which. When a tool drafts a change, it checks which flows, Apex or validation rules touch those fields and says so. It never applies the change itself. You run it.
It is a standard Streamable HTTP MCP server, so any MCP-compatible client can connect. We build and verify against Claude Code. ChatGPT, Copilot, Cursor, Gemini, Goose, LibreChat, Open WebUI and Windsurf implement the same surface, and we have not tested those ourselves.
Clientell MCP is in early access. There is no self-serve signup yet, so the token comes from the team directly. Once you have one, install is a single command and takes about a minute.
Yes. You set an active org for the session and every result names the org it came from. Developer orgs, sandboxes and production all work the same way, and each org is indexed separately.
Any MCP-compatible client can connect
Connects instantly with a single secure API token — no local server setup required. Works out of the box with Claude Code, Cursor, and any MCP-enabled AI tool or IDE.
Built by the team behind Clientell’s Salesforce agent, deployed in 2000+ Salesforce orgs.