2 Nov 2026 · Salesforce DX MCP support ends

DX MCP is ending. Don’t just replace it. Give your agent the bigger picture.

Moving off DX MCP? Keep your AI client and sf CLI. Connect Clientell MCP to build Flows, debug Apex, manage reports, audit your org, and plan safer deployments with full Salesforce context.

$249 a month for 10 people. 14-day free trial, no credit card.

Prefer a walkthrough?Book a demo

Claude Code
Codex
Cursor
VS Code
Claude Desktop
Claude Cowork

Your upgrade⁽⁰⁴⁾

The upgrade

Same workflow. Now it knows your org.

Keep investigating Apex issues and shipping deploys. Now your agent also sees how your org connects before it touches anything.

Start free trial

Find the Flow before it breaks
See the Flows and Apex triggers touching a field before you change it, not after it breaks in production.
Catch the deploy that wipes access
When Clientell prepares a Profile, Permission Set or Sharing Rule deploy, it refuses one that would wipe existing entries.
Stop chasing dependencies by hand
Ask what references a field, Flow or object, and get the answer from your org's metadata.
Approval before production
Clientell drafts and checks the change. Your sf CLI deploys it once you approve.

What carries over: your sf CLI login still runs deploys and live checks. Your AI client doesn't change.

Side by side

What changes when you move

DX MCP's deploy and SOQL tools stay real strengths. Here's what Clientell MCP adds on top, and what sf-skills covers instead.

Start your free trial

Salesforce DX MCP, sf-skills and Clientell MCP compared
	DX MCP (@salesforce/mcp)	sf-skills	Clientell MCP
What it is	A local MCP server wrapping sf CLI tools. More than 60 tools across the development lifecycle.	Instructions and scripts, not a server	A hosted MCP server: a Context Graph of your org's metadata
Deploy and retrieve metadata	Yes, directly. Metadata retrieve and deploy, including Apex.	Yes, via sf CLI commands it runs	Drafts the change and checks its blast radius; your AI client deploys through your own sf CLI session after you approve
SOQL queries, Apex tests	Yes. SOQL, permission set assignment, Apex test runs.	Yes, via sf CLI	Live record reads on your own connection. Apex tests run through your sf CLI.
See what a change would affect first	No, you check manually	No	Yes. Traces the Flows, Apex, validation rules, profiles and permission sets connected to what you're about to touch
Where it runs	Local process on your machine, via npx against an org your sf CLI is already authenticated to.	Inside your AI client, via your sf CLI	Hosted. Your sf CLI still handles deploys and live checks
Status after 2 Nov 2026	None. Repos archived, no fixes	Salesforce's current suggested path	Actively maintained

Setup

Move in four steps

No migration tool. We don't import your DX MCP settings. Get a token, add one entry to your client, verify it connects.

Client

Claude Code

Config file

~/.claude.json

Connects to

https://mcp.clientell.ai/mcp

Get your token

Step 1: Get your token
Sign up, authorize Salesforce, let the first index build, then copy your workspace token.

Pick your client

Use --scope user so it works in every project.

02
Step 2: Remove DX MCP Optional
You can run both at once while you compare answers. Remove the @salesforce/mcp entry only once nothing depends on it.
1. Run claude mcp list and find the entry that runs @salesforce/mcp.
2. Remove it by name, using the scope it was added with (local, project or user).
3. Project-scoped entries live in the repository's .mcp.json.
Terminal
```
claude mcp list
claude mcp remove "<name>" -s <scope>
```
03
Step 3: Add Clientell
Paste one command or config block into your client, with your token in the Authorization header.
Terminal
```
claude mcp add-json clientell '{
  "type": "http",
  "url": "https://mcp.clientell.ai/mcp",
  "headers": { "Authorization": "Bearer <YOUR_TOKEN>" },
  "timeout": 180000
}' --scope user
```
- Keep the word Bearer and the space after it when you paste your token.
- Claude Code does not test the URL or token when saving the entry. Verify the connection next.
04
Step 4: Verify
1. Expect Status: ✔ connected.
2. Then open Claude Code and paste this setup prompt: Set up Clientell AI. Check for the Salesforce CLI first and ask before installing anything if it is missing, then walk me through picking my org. When the org graph is ready, call clientell_start.
Terminal
```
claude mcp get clientell
```

Edit claude_desktop_config.json and restart. It only reads the file at launch.

02
Step 2: Remove DX MCP Optional
You can run both at once while you compare answers. Remove the @salesforce/mcp entry only once nothing depends on it.
1. Open ~/Library/Application Support/Claude/claude_desktop_config.json.
2. Delete the server entry whose "args" include "@salesforce/mcp".
3. Save the file. Leave every other entry as it is.
03
Step 3: Add Clientell
Paste one command or config block into your client, with your token in the Authorization header.
claude_desktop_config.json
```
{
  "mcpServers": {
    "clientell": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@0.14.3",
        "https://mcp.clientell.ai/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}
```
- This entry runs the mcp-remote bridge, so it needs Node.js 18 or higher. Check with node --version.
- Quit Claude Desktop fully and reopen it after saving. It reads this file only at launch.
- The token sits in this file in plain text, so keep the file private.
04
Step 4: Verify
1. Save the file, then quit Claude Desktop fully and reopen it.
2. Open your client's MCP server list and confirm clientell is connected.

Add a custom connector under Customize, then Connectors, with the server URL and an Authorization: Bearer <token> header.

Step 2: Remove DX MCP Optional
You can run both at once while you compare answers. Remove the @salesforce/mcp entry only once nothing depends on it.
Nothing to remove here. DX MCP is a local server, and Claude Cowork only adds remote connectors.
03
Step 3: Add Clientell
Paste one command or config block into your client, with your token in the Authorization header.
1. In the Claude desktop app, go to Settings > Connectors and add a custom connector. Name it Clientell, paste the server URL, ending in /mcp, and set Authentication to "None".
2. Under Advanced settings > Request headers, add a header. Name: Authorization. Value: Bearer <YOUR_TOKEN>. Save.
Connector settings
```
URL: https://mcp.clientell.ai/mcp
Authorization: Bearer <YOUR_TOKEN>
```
- Pro, Max, Team and Enterprise plans.
- Request headers are in beta. If you don't see them, your organization doesn't have access yet. Use a tool on your computer for now.
- Already added it in claude.ai? It's already in Cowork.
04
Step 4: Verify
1. In a Cowork task, open + > Connectors and switch Clientell on.
2. Open your client's MCP server list and confirm clientell is connected.

Add a custom connector in claude.ai under Settings, then Connectors, with the server URL and an Authorization: Bearer <token> header.

Step 2: Remove DX MCP Optional
You can run both at once while you compare answers. Remove the @salesforce/mcp entry only once nothing depends on it.
Nothing to remove here. DX MCP is a local server, and claude.ai only adds remote connectors.
03
Step 3: Add Clientell
Paste one command or config block into your client, with your token in the Authorization header.
1. In claude.ai, go to Settings > Connectors and add a custom connector. Name it Clientell, paste the server URL, ending in /mcp, and set Authentication to "No sign-in".
2. Under Advanced settings > Request headers, add a header. Name: Authorization. Value: Bearer <YOUR_TOKEN>. Save.
Connector settings
```
URL: https://mcp.clientell.ai/mcp
Authorization: Bearer <YOUR_TOKEN>
```
- Pro, Max, Team and Enterprise plans.
- Request headers are in beta. If you don't see them, your organization doesn't have access yet. Use a tool on your computer for now.
04
Step 4: Verify
1. In a chat, open + > Connectors and switch Clientell on.
2. Open your client's MCP server list and confirm clientell is connected.

Add this block to ~/.codex/config.toml, with your token in the Authorization header.

02
Step 2: Remove DX MCP Optional
You can run both at once while you compare answers. Remove the @salesforce/mcp entry only once nothing depends on it.
1. Open ~/.codex/config.toml.
2. Delete the [mcp_servers.<name>] table that runs @salesforce/mcp.
3. Save the file. Leave every other table as it is.
03
Step 3: Add Clientell
Paste one command or config block into your client, with your token in the Authorization header.
config.toml
```
[mcp_servers.clientell]
url = "https://mcp.clientell.ai/mcp"
http_headers = { Authorization = "Bearer <YOUR_TOKEN>" }
```
- Needs the current Codex CLI (Rust build) with MCP support. The 2025 TypeScript preview cannot connect. Check with codex --version.
04
Step 4: Verify
1. Open your client's MCP server list and confirm clientell is connected.

Add the server to ~/.cursor/mcp.json for every project, or a project-local .cursor/mcp.json to scope it to one repo.

02
Step 2: Remove DX MCP Optional
You can run both at once while you compare answers. Remove the @salesforce/mcp entry only once nothing depends on it.
1. Open ~/.cursor/mcp.json (or .cursor/mcp.json in the project).
2. Delete the server entry whose "args" include "@salesforce/mcp".
3. Save the file. Leave every other entry as it is.
03
Step 3: Add Clientell
Paste one command or config block into your client, with your token in the Authorization header.
mcp.json
```
{
  "mcpServers": {
    "clientell": {
      "url": "https://mcp.clientell.ai/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}
```
- Put it in ~/.cursor/mcp.json instead to add it for every project.
- Cursor caps tools at about 40 across all servers.
04
Step 4: Verify
1. Open your client's MCP server list and confirm clientell is connected.

Add it under the top-level servers key in .vscode/mcp.json, not mcpServers. That's the one place this client differs.

02
Step 2: Remove DX MCP Optional
You can run both at once while you compare answers. Remove the @salesforce/mcp entry only once nothing depends on it.
1. Open .vscode/mcp.json (top-level key: servers).
2. Delete the server entry whose "args" include "@salesforce/mcp".
3. Save the file. Leave every other entry as it is.
03
Step 3: Add Clientell
Paste one command or config block into your client, with your token in the Authorization header.
mcp.json
```
{
  "servers": {
    "clientell": {
      "type": "http",
      "url": "https://mcp.clientell.ai/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}
```
- VS Code uses servers as the top-level key, not mcpServers. If the server does not show up, check that key first.
04
Step 4: Verify
1. Open your client's MCP server list and confirm clientell is connected.

FAQ

Questions

Can I keep DX MCP?

Yes. Pinned versions keep working after 2 Nov 2026 because the npm package stays installable. Nobody fixes a bug or a changed login flow after that date. You can run both side by side while you compare.

Do my sf CLI orgs carry over?

Your sf CLI login keeps handling deploys and live checks. The graph needs a one-time Salesforce authorization in Clientell.

What does Clientell MCP actually do?

It builds a Context Graph of your org: objects, fields, flows, Apex, validation rules, profiles and permission sets, and how they reference each other. Ask what a change would touch before you make it, read live records on your own connection, and get asked before anything reaches production.

Is my data safe?

Your org's metadata builds the Context Graph. Live record reads happen on your own Salesforce connection when you ask, and pass straight back to your client; they aren't stored. The Salesforce connection itself is stored encrypted (AES-256-GCM) and serves only your own reads, never a teammate's.

Do I need admin rights?

To install the Clientell managed package in your org, yes, a Salesforce admin does that once.

Still on DX MCP?

Move to Clientell MCP.

Your sf CLI login carries over. Clientell MCP adds the org context DX MCP never had.

No DX MCP settings to migrate. Start with your work email.

$249 a month for 10 people. 14-day free trial, no credit card.

Or book a demo

DX MCP is ending. Don’t just replace it. Give your agent the bigger picture.

Your upgrade(04)

Same workflow. Now it knows your org.

Find the Flow before it breaks

Catch the deploy that wipes access

Stop chasing dependencies by hand

Approval before production

What changes when you move

Move in four steps

Step 1: Get your token

Step 2: Remove DX MCP Optional

Step 3: Add Clientell

Step 4: Verify

Step 2: Remove DX MCP Optional

Step 3: Add Clientell

Step 4: Verify

Step 2: Remove DX MCP Optional

Step 3: Add Clientell

Step 4: Verify

Step 2: Remove DX MCP Optional

Step 3: Add Clientell

Step 4: Verify

Step 2: Remove DX MCP Optional

Step 3: Add Clientell

Step 4: Verify

Step 2: Remove DX MCP Optional

Step 3: Add Clientell

Step 4: Verify

Step 2: Remove DX MCP Optional

Step 3: Add Clientell

Step 4: Verify

Questions

Move to Clientell MCP.

Your upgrade⁽⁰⁴⁾