The Salesforce MCP that knows what your change touches

Know your org. Check the change. Keep control.

Ask your AI client what depends on a field, inspect a live record when needed, and keep decisions across conversations. The hosted MCP server connects these three parts. There is no local server to install.

Call all twelve connectors directly over MCP from your client. No separate Clientell agent is required.

Deep org context, with clear boundaries.

See what your client can act on, where the data stays, and which safeguards apply before a change reaches Salesforce.

See the blast radius before you make a change.

The Context Graph maps your org’s components and their references. Ask what depends on Account.Custom_Segment__c before you delete it. Get the affected flows and permissions from the graph, not a series of live API calls.

Objects, fields, flows, Apex, validation rules, profiles and permission sets, with their references. Ask which flow writes to a field, which profiles can edit it, or what a deletion would break. The graph answers structural questions without reading customer records.

Clientell patches the proposed change and audits its impact against the graph. When Clientell prepares a deploy, deploy_guard checks it and refuses unsafe replace-not-merge payloads for Profiles, Permission Sets and Sharing Rules. Once you approve, your AI client runs the deploy through your own sf session, under your credentials and permissions. Duplicate-record merges get the same care: merge_duplicate_records verifies every record ID against the org and drafts a merge plan it can prove safe, so the merge is checked before anything is deleted. The merge then runs through your own sf session.

Always know how fresh an answer is.

Every graph answer carries its last_graph_build timestamp. Rebuild the Salesforce graph whenever you want with one call, and confirm any Flow, Apex or validation-rule answer against the live org in one command.

Call clientell_set_active_org with no arguments to rebuild the graph after you change metadata. Answers about Flows, Apex classes, validation rules and other components come with a ready-to-run sf command that checks whether they changed in the live org since the last build. Connectors read the source system at question time, so their answers are current by design. Live Salesforce record lookups run when you ask, through Clientell’s auth service on your own Salesforce connection and permissions. The records pass through to your client and are not stored.

Your workspace is isolated. Your CLI stays yours.

Check who can query the graph, how writes are approved, and which credentials Clientell stores before connecting a production org.

Use the MCP client you work in.

Clientell exposes tools and instructions over Streamable HTTP MCP with bearer auth. It is built and verified end to end on Claude Code, and works with any Streamable HTTP MCP client, including Cursor, VS Code, ChatGPT and Gemini.

This is not an allowlist. Any client supporting Streamable HTTP MCP with bearer auth can register the server. Claude Code is the client Clientell builds and verifies against end to end.

Connect Salesforce and ask your first question.

Authorize Salesforce, build your first Context Graph, then register Clientell in your MCP client. The worked commands below are for Claude Code.

claude --version

sf --version

sf org list

claude mcp add-json clientell '{
  "type": "http",
  "url": "https://mcp.clientell.ai/mcp",
  "headers": { "Authorization": "Bearer <YOUR_TOKEN>" },
  "timeout": 180000
}' --scope user

claude mcp add --transport http clientell https://mcp.clientell.ai/mcp \
  --header "Authorization: Bearer <YOUR_TOKEN>" \
  --scope user

Register the same hosted endpoint in your client’s config. Any Streamable HTTP MCP client works; these snippets cover the common ones, and the worked Claude Code path above is the one Clientell verifies end to end. See Supported clients, and check your client’s current documentation if its config format has changed.

{
  "mcpServers": {
    "clientell": {
      "type": "http",
      "url": "https://mcp.clientell.ai/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

[mcp_servers.clientell]
url = "https://mcp.clientell.ai/mcp"
http_headers = { Authorization = "Bearer <YOUR_TOKEN>" }

{
  "mcpServers": {
    "clientell": {
      "url": "https://mcp.clientell.ai/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

{
  "servers": {
    "clientell": {
      "type": "http",
      "url": "https://mcp.clientell.ai/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Confirm your client can reach the graph.

Check the connection before asking about your org. Registering saves the entry; the first connection tests the endpoint and token.

The fast check

Check Clientell alone for a quick status.

claude mcp get clientell

The full check

Check every configured MCP server. This can take 30 to 60 seconds, or longer if another server is unresponsive.

claude mcp list

Every status this can report

On older Windows consoles the marks render as √ and × instead of ✔ and ✘. Same meanings.

Inside a session

Start Claude Code and type /mcp. You will see clientell listed with its tools.

Start with a field you need to change.

Ask your AI client a plain-language question about your org. It chooses the relevant tools and answers from the graph.

• What writes to Opportunity.Amount?Find flows, Apex, validation rules and processes that touch this field before editing it.
• What breaks if I delete Account.Custom_Segment__c?Check references and impacted components before removing the field.
• Show me every flow on Case that fires after save.Compare after-save automation on one object.
• Which profiles can edit Contact.Email?Inspect field access across profiles and permission sets.

A first question against a cold graph can take a while. If it runs past about two minutes, Claude Code moves it to a background task and tells you so. Answers are sized to fit your AI client’s context, and a sized answer says so and reports the full count. Ask a narrower question or page through for more.

Choose the org before trusting the answer.

Working across production and sandboxes? Set the active org so dependency answers come from the index you intended.

Salesforce context, plus the work around it.

Salesforce provides the metadata map. Eleven more connectors read the work around it, live, at question time: Slack, Jira, GitHub, Gmail, Google Calendar, Google Drive, Notion, Microsoft Teams, SharePoint, Outlook Mail and Outlook Calendar. Each one reads as you, through your own grant.

• list_connector_capabilitiesLists your connected providers, their status, and the actions and arguments use_connector accepts for each.
• use_connectorRuns a live read or action on a connected provider through your own account. Salesforce, when listed, is read-only: query, describe and limits.

Call all twelve connectors directly over MCP from your client. No separate agent surface is required.

Find dependencies, plan changes, check impact.

These nine tools answer org questions, draft changes and surface context. The server patches and audits proposed changes; after approval your AI client deploys through your own sf session. The duplicate-record merge tool proves a merge is safe before anything is deleted. /mcp also lists the setup tools below and the active connector tools.

• search_salesforce_metadataTrace objects, fields, flows, rules and permissions. See what depends on a component before you change it, with curated audit sections when needed.
• get_salesforce_best_practicesGet vetted guidance before building a Flow, writing a validation rule or loading data.
• build_or_fix_salesforce_flowDraft a Flow from a plain-language request or diagnose a runtime error and propose a fix. Clientell patches and audits the change; approved deploys run through your AI client's own sf session.
• search_salesforce_docsFind the relevant Salesforce documentation and cite the source guide.
• generate_salesforce_org_reportGenerate an impact, audit or access report you can inspect and share.
• search_team_contextSearch your team's email, Slack, Jira, meetings and documents for the people and decisions behind a Salesforce change, plus the context saved with clientell_remember.
• find_person_in_salesforce_and_workFind a person across Salesforce and your team's email, Slack and Jira context, and say with an explicit confidence whether the records are the same human. Only an exact email match links automatically; anything weaker comes back as a question for you.
• merge_duplicate_recordsFind duplicate Accounts, Contacts or Leads, verify every record ID against the org and draft a merge plan it can prove safe before anything is deleted. The merge runs through your own sf session.
• manage_salesforce_reports_dashboardsBuild, update, run or delete native Salesforce Reports and Dashboards, including joined reports. It checks each report against the report type's real columns and hands back the exact sf command. You run it.

Use these /mcp tools to connect and select an org, add integrations, manage billing and memory, confirm identity links, run playbooks and delete workspace data.

• clientell_onboarding_statusCheck connected systems and whether your workspace index has been built.
• clientell_connect_salesforceConnects a Salesforce org from your terminal when none is connected yet. It returns a link you open in the browser, then a second call confirms the connection.
• clientell_set_active_orgSets which Salesforce org the session is working against. See Picking the right org.
• clientell_add_integrationConnects Slack, Gmail or Jira to your workspace. It returns an authorization link, then a second call confirms the connection.
• clientell_billing_statusReports the billing state of your workspace.
• clientell_upgradeStarts an MCP ($249/mo) or Platform ($500/mo) subscription through Stripe Checkout, or opens the billing portal if you already subscribe. Nothing is charged until you finish checkout.
• clientell_delete_my_dataDeletes the data held for you. See Uninstall and data deletion.
• clientell_rememberSave work context explicitly. Nothing is stored automatically from your activity.
• clientell_confirm_person_linkRecords your answer when find_person_in_salesforce_and_work asks whether two records are the same person, so it is not asked again. A wrong link can be undone.
• clientell_push_work_recordsDemo bridge, not a live sync: indexes Gmail, Jira or local SFDX project records your AI client has already read. Only index fields are accepted, never message bodies or file contents.
• run_clientell_playbookRuns a named Clientell playbook, such as standup or plan_data_load, for clients that cannot show this server's MCP prompts.

Connect a person across work systems.

Link a Salesforce User, Slack member and Jira account when their identifiers share a signal. Use that association to follow related work across connected systems.

Keep the decisions worth carrying forward.

Record why you made a change, then find that context in a later conversation. You or the model must explicitly call clientell_remember to save an entry.

Find the error. Take the next step.

Start by checking whether the endpoint responds. Then match the status or error below to a specific fix.

Disconnect the client. Delete the workspace data.

Remove the server entry to stop using it in Claude Code. Delete the data held for you separately, then revoke any connector authorizations you no longer need.

claude mcp remove clientell -s user

Before removing the server, ask your client to call clientell_delete_my_data to delete the data held for you. Removing a client configuration does not delete its underlying workspace data.

Quick answers before you connect.

Find the key details on record data, graph permissions, deployment, connectors and supported clients.

Keep building with context.

• Clientell MCPSee how the Salesforce Context Graph and change checks work, with the benchmark and a comparison to hosted MCP servers.
• PricingMCP plan from $249/mo for 10 people on one org (+$25 per extra person), Platform $500/mo, and 14-day free trial with no credit card.
• BenchmarkA mean graded score of 86.5% with the graph and 44.2% without it, and how the test was run.
• AI Context LayerExplore the Context Graph behind Clientell MCP and other ways to use it.
• Compared to Salesforce's hosted MCPCompare the two Salesforce MCP approaches and when to use them together.
• Contact usGet help with setup, access, or a server-side failure.

Changes to this document.

Material changes to what this page claims. Wording fixes and typography are not listed.

• 26 Sep 2026

  Lists all twelve live connectors with their verified access levels. HubSpot is no longer listed. Explains graph freshness through last_graph_build and the live checks that come with Flow, Apex and validation-rule answers.

• 25 Sep 2026

  Clarifies the approved Salesforce deploy workflow, deploy guard and duplicate-merge boundary. Setup includes the managed-package prerequisite and the external_app_not_installed recovery path.

• 21 Sep 2026

  First published with setup steps, connector status, graph security, identity resolution and memory guidance.

Connector status reflects what is available today. All twelve listed connectors are live.