Skip to content
Connector Scout
–saved records

Claude · Salesforce

Does Salesforce connect to Claude?

Yes, but it is explicitly a beta. Anthropic's Connectors Directory lists 'Salesforce - Beta', built by Salesforce and implemented through Salesforce's Headless 360 MCP Server, with capabilities described as 'Read & write.' It documents retrieving pipeline, account and case data, and creating a campaign appears among its examples. Broader object-wide creation, update or deletion is not documented, so treat those as unconfirmed rather than assumed, and expect the usual beta caveats around stability and availability.

Limited rolloutDocumentation verifiedLast verified 9 Sept 2026MCP server
Compare connections

Quick answer

Yes — Salesforce connects to Claude as a mcp server, verified against official documentation on 9 Sept 2026. Documentation confirms search, read and create access, while update, delete, sync, interactive and send remain not confirmed — which is different from unavailable. Yes, but it is explicitly a beta.

Relationship
Official and documentation-verified
Confirmed access
Search, Read and Create · update, delete, sync, interactive and send not confirmed
Plan or account
A Salesforce account with an assigned profile and permission sets covering the pipeline, account and case data in question
Setup and admin
Claude Connectors Directory
Last verified
9 Sept 2026
Best fit or limit
This is a beta connector; Anthropic can change its capabilities, stability or availability without the same guarantees as generally available connectors.

What it is

The Salesforce connector is published in Anthropic's Connectors Directory under the label 'Salesforce - Beta,' is built by Salesforce, and is implemented through Salesforce's Headless 360 MCP Server rather than a generic Anthropic integration. Anthropic's listing describes 'Read & write' capabilities and documents retrieving pipeline, account and case data; campaign creation appears among the connector's examples, indicating a specific, named write capability rather than blanket create access across every Salesforce object. Because it is a beta, its behavior, availability and capability set should be expected to change, and it should not be treated as having the same stability guarantees as generally available connectors. Access through the connector remains bounded by the connecting user's Salesforce profile, permission sets, sharing rules and field-level security, so Claude cannot see or change more than that user's own Salesforce session already allows.

Connection type Salesforce-built Claude connector (Beta), implemented through Salesforce's Headless 360 MCP Server

What it can do

What it cannot do

Not confirmed means official documentation does not assign this capability to this specific connection. It is not a claim that the capability is impossible.

Every status is defined the same way across the site — see how connector capabilities are defined and evidenced.

Availability and requirements

Listed in Anthropic's Connectors Directory as 'Salesforce - Beta,' built by Salesforce and implemented through Salesforce's Headless 360 MCP Server. Beta status means capabilities, stability and rollout can change; confirm the current directory listing before depending on it for a workflow.

Account requirements

  • A Salesforce account with an assigned profile and permission sets covering the pipeline, account and case data in question
  • A Claude account on a surface where the beta connector is listed

How to connect

Setup path Claude Connectors Directory

  1. 1. Open the Connectors Directory

    Browse to the 'Salesforce - Beta' listing in Claude's Connectors Directory.

  2. 2. Confirm beta status

    Review the beta label and current documented capabilities before committing a workflow to it.

  3. 3. Connect and authenticate

    Connect the Salesforce account whose profile and permission sets should apply.

  4. 4. Start with a read-only question

    Ask a pipeline, account or case retrieval question first so the connected scope is clear.

  5. 5. Scope any write use narrowly

    Limit write reliance to the documented example (campaign creation) rather than assuming broader write access.

Permissions, privacy, and admin controls

Anthropic documents that Team and Enterprise organization owners may need to enable a connector before members authenticate it. Salesforce-side administrators separately control what the connecting user's profile, permission sets and sharing rules expose.

  • Access is bounded by the connecting user's Salesforce profile, permission sets, sharing rules and field-level security; Salesforce governance, not the connector, remains the controlling boundary on what Claude can reach.
  • Anthropic documents that connectors inherit each person's existing permissions in the source service, so an account with broad Salesforce access produces correspondingly broad Claude reach.
  • Because this is a beta implemented through a Salesforce-operated MCP server, treat write actions (such as campaign creation) with the same caution as any other business-system write and confirm results in Salesforce directly.

Platform context

  • Claude web connectors are generally available across Claude surfaces, but individual connector requirements differ. Claude inherits the connected user’s permissions from the source service. Team and Enterprise organization owners may need to enable a connector before members authenticate it.

Documented limitations

  • This is a beta connector; Anthropic can change its capabilities, stability or availability without the same guarantees as generally available connectors.
  • Object-wide update and delete across Salesforce records are not documented and should not be assumed.
  • Creation is documented for campaigns specifically; broader record creation across other Salesforce objects is unconfirmed.
  • Claude sees only what the connecting Salesforce user's profile, permission sets, sharing rules and field-level security already expose; nothing beyond that session's access is reachable.
  • Directory listings change; re-check capabilities before a recurring workflow depends on them.

Best use cases

  • Pulling a quick pipeline or account summary without opening Salesforce directly
  • Reviewing open case data for a named account during a conversation
  • Drafting and creating a new marketing campaign from a conversation
  • Cross-referencing Salesforce account data with information from other connected tools

Example prompts

  • “What's the current status of the pipeline for the Acme account?”
  • “Summarize the open cases for our largest customer this quarter.”
  • “Create a campaign for the upcoming product launch.”
  • “Pull the account details for the deals closing this month.”

Troubleshooting

  • Claude can't see a Salesforce record that should be visible.

    Check the connecting user's Salesforce profile, permission sets, sharing rules and field-level security; the connector only reaches what that user's own session already allows.

  • A write action beyond campaign creation didn't work as expected.

    Only campaign creation is documented as a specific write example; broader create, update or delete behavior is unconfirmed for this beta connector and may not be supported.

Official sources

Verification history

Last verified 9 Sept 2026 · next review 9 Oct 2026 · Connector Scout editorial research

  1. 9 Sept 2026Promoted from research pending to documentation verified against Anthropic's current Salesforce connector listing.

Documentation verified — editorial disclosure

Documentation verified means Connector Scout confirmed the connection and listed capabilities against official provider documentation. It does not mean Connector Scout completed hands-on testing in a live account.

Independence notice

Connector Scout is not affiliated with Anthropic or Salesforce. Confirm security-sensitive details against the vendor’s own documentation before rolling out access.