Skip to main content
Clientell MCP / Cursor

Use Clientell MCP in Cursor with your Salesforce org

Clientell MCP is a hosted Salesforce MCP server. In Cursor you register it as one entry in mcp.json. Cursor’s agent can then ask the org context graph which flows, Apex triggers, validation rules and permissions touch a field, while your Salesforce project is open in the editor.

Client version and last checked

Config format checked against Cursor’s MCP documentation (cursor.com/docs/context/mcp) on 28 Oct 2026. Cursor version: not recorded yet. We have not published a recorded Cursor session, so this page does not show one. The steps below are the config from our documentation.

What the MCP adds to Cursor

Cursor reads your repo. The MCP reads your org.

An SFDX project in Cursor shows the metadata you have retrieved. It does not show what else in the org depends on a field, and a retrieve can be partial or stale. The org context graph is an index of names, identifiers, metadata and relationships, so the agent can ask the org instead of guessing from the files in front of it.

  • What touches Opportunity.Amount?Flows, Process Builder, Workflow Rules, Apex triggers and validation rules that use one field, including ones that are not in your repo.
  • Which profiles can edit Contact.Email?Field-level security resolved across profiles and permission sets.

Answers like these use metadata, not record contents. On a metadata-question benchmark, the same model’s graded score was 86.5% with the context graph against 44.2% without it. Method and data are on the benchmark page.

Install config

One entry in mcp.json.

Cursor reads MCP servers from ~/.cursor/mcp.json for your whole account, or .cursor/mcp.json inside a repository for that project only. Add the entry below, replace the token placeholder, and reload Cursor if the server does not appear.

mcp.json
{
  "mcpServers": {
    "clientell": {
      "url": "https://mcp.clientell.ai/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}
  • url ends in /mcp. That suffix is part of the address.
  • Authorization keeps the word Bearer and the space after it. The token is a Clientell AI workspace credential, not a Salesforce credential. You get it from the Clientell AI web app after you start the trial.
  • This entry has no type key. The Claude Code command needs one, Cursor’s remote-server format does not.
Do not commit the token

A project-level .cursor/mcp.json sits inside your repository. With the token pasted in, a commit publishes it to everyone who can read the repo. Use the account-level file, or add .cursor/mcp.json to .gitignore first.

Full setup for every client, including the tool reference, is in the documentation.

Worked prompt

Check the org before the agent edits your repo.

This is a prompt to paste into Cursor’s agent chat with an SFDX project open. It is the shape of the request, not a recorded result.

Cursor agent prompt
I want to rename Account.Custom_Segment__c to Account.Customer_Tier__c.
Before you change any files in this repo, use the clientell MCP to list
everything in the org that reads or writes Account.Custom_Segment__c:
Flows, Process Builder, Workflow Rules, Apex triggers, validation rules
and permissions. Then compare that list with what exists in force-app
and tell me which dependents are not in this repository. Do not edit anything yet.

What to look for in the response:

  • The agent calls search_salesforce_metadata on the Clientell server instead of grepping force-app alone.
  • It separates dependents it found in your files from dependents that exist only in the org.
  • If the answer is marked truncated, treat it as incomplete and narrow the question.
  • Check the answer against the org before you rename anything.

Any change after that is yours to approve, and it runs through your own sf CLI on your machine. For the same kind of question asked from a terminal, see the Claude Code page.

Known issues

What goes wrong in Cursor, and what it means.

The server shows an error or never lists tools
What it means

Cursor saved the file but could not reach the endpoint or was rejected by it.

Fix

Check the URL ends in /mcp, then check the token. A stray space or newline copied with the token is sent as part of it and the server answers 401. Re-copy the token and paste it again.

Nothing changed after editing mcp.json
What it means

Cursor may not have re-read the file.

Fix

Reload the Cursor window. If the server still does not appear, check you edited the file you meant to: the account-level file and a project file are two different entries.

The answer looks short, or a count seems too low
What it means

Large results get cut. The server caps its own output first and marks the result as truncated, with the true row count beside the rows returned.

Fix

Narrow the question and ask again. Do not act on the number from a truncated answer.

The agent answered about the wrong org
What it means

Selecting an org in the conversation is not built yet. Today the server binds to the org your token belongs to, and says so when that is ambiguous.

Fix

If you are signed in to several orgs, run sf org list and confirm which one your Clientell AI workspace is connected to before you rely on an answer.

Slow first answer
What it means

A first question against a cold org graph can take a while.

Fix

We have not measured how Cursor handles long tool calls, so we make no claim about its time limit. If a first call fails after a long wait, retry once.

What it does not do

Deploys go through your own tools.

The MCP answers questions about the org and proposes changes. It does not replace your deploy pipeline, and it does not run the Salesforce DX server’s build and test tools. Changes to your org run as sf commands from your machine, and Clientell AI asks before it changes anything in production.

The index holds names, identifiers, metadata and relationships, not Salesforce record contents. The Salesforce connection you authorise is stored encrypted and serves live reads only for you. Your local Salesforce CLI session is separate and stays on your machine. Longer version in the security section.

FAQ

Questions people ask.

Does Cursor work with the Clientell AI MCP server?

Yes. The Clientell AI MCP server works in Claude Code, Claude Cowork, Codex, Cursor and VS Code. In Cursor you register the hosted endpoint with one entry that holds your workspace token.

Does Cursor get my Salesforce password or session?

No. The token is a credential for your Clientell AI workspace. It is not a Salesforce credential and cannot be used to reach Salesforce. You authorize Salesforce in the Clientell AI web app.

Can I use the Salesforce DX MCP server in Cursor instead?

It reached end of life on 2 November 2026. Salesforce says the npm package stays installable and a pinned 0.30.15 setup keeps working, but nothing more ships. Salesforce points developers to skills at forcedotcom/sf-skills.

Keep going

Related pages.