Salesforce - Beta

Salesforce's Headless 360 beta has four tools reaching the whole platform.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Salesforce - Beta connector does

Salesforce's Headless 360 MCP server connects a Salesforce org to Claude, ChatGPT and any MCP client over OAuth. It exposes four tools — but the count is misleading. Two of them look up operations, and dispatch then runs whichever Salesforce operation the agent picked at runtime. The reachable surface is the platform, not four functions. It is a Beta service.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Salesforce - Beta tools (4)

  • describe
  • discover
  • dispatch
  • dispatch_readonly

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • We did not read this server's tools. Our anonymous handshake was refused: the endpoint returned HTTP 401 with the body {"errors":[{"message":"JWT Token is required"}]} to an anonymous initialize on 2026-09-08, which is the live check that established the OAuth posture. The four tool names come from Anthropic's directory listing and Salesforce's own reference page, not from a handshake. We have not seen the server's annotations, so this page makes no claim about readOnlyHint or destructiveHint values on the live tools.
  • Beta, with terms attached. Salesforce labels the Headless 360 MCP Server a Beta Service available from July 2026, states that use is at your sole discretion, and makes it subject to the applicable Beta Services Terms. Salesforce separately documents that beta server URLs and beta OAuth scopes stop working at GA and require reconnection.
  • The tool count is not the capability. Salesforce states the operation library grows each release, so what dispatch can reach on the day you read this is not what it could reach at beta launch. Call discover to see the current set; no static list on this page or any other can be authoritative.
  • The operation library started narrow. Salesforce states that at beta launch the server offers "dozens of operations", most focused on Setup tasks for admins — not the full platform.
  • Scope cannot separate read from write. The protected-resource descriptor returns mcp_api and refresh_token for this endpoint, the same pair for every tool. Restricting an agent to dispatch_readonly is a client-side configuration, not an OAuth grant.
  • The connector inherits, and does not reduce, your permissions. Salesforce's guarantee is that the agent cannot exceed the signed-in user. An org connected by a System Administrator gives the agent administrator reach.
  • Rate limits are your org's, not the server's. Salesforce documents that tools run as the authenticated user under the same rate limits as any REST call by that user. No separate MCP quota is published, so MCP traffic consumes the org's normal API allocation.
  • Edition and version gates apply. Salesforce requires API version v67.0 or later, and its connection troubleshooting asks you to confirm the org edition supports API access, naming Developer or Enterprise, or Professional with API access enabled.
  • Setup is not one click. An External Client App is required — Connected Apps are explicitly not supported — the app can take up to 30 minutes to become operational, and a Salesforce administrator must activate the server before any client can connect.
  • Scratch orgs need a workaround. Salesforce states External Client Apps cannot be created directly in scratch orgs through the Setup UI; you build the app in a Dev Hub org, package it, and install the package.
  • A three-year support floor, not a permanent one. Salesforce commits to supporting each hosted MCP service version for at least three years from first release, with at least one year's notice before a version is retired, and states tools may be upgraded or replaced between releases.

Frequently asked questions

Does the Salesforce Headless 360 MCP server let an agent do more than I can?

No. Salesforce's documentation states that every Hosted MCP transaction runs as the authenticated user, and that object permissions, field-level security, sharing rules, profile permissions and permission sets all apply. Its wording is direct: if you cannot perform an action in Salesforce, your agent cannot perform it through the MCP server. Audit trails attribute every action to you.

What is the difference between dispatch and dispatch_readonly?

The HTTP methods each accepts. Salesforce's request schema for dispatch permits GET, POST, PUT, DELETE and PATCH, so it can create, update and delete. The schema for dispatch_readonly restricts the method enum to GET alone, and Salesforce states the tool never changes data or configuration. Both take a URL and route through the same access guard.

Why does the Headless 360 MCP server only have four tools?

Because it is a dispatcher, not a fixed toolset. Salesforce's documentation states that instead of exposing thousands of features as individual tools, the server provides four tools backed by a continuously growing library of Salesforce operations. The tool surface stays small and stable while the set of actions the agent can take scales independently of it.

What does Beta mean for the Salesforce Headless 360 MCP server?

It means the service is optional and governed by separate terms. Salesforce states the Headless 360 MCP Server is a Beta Service available from July 2026, that you use it at your sole discretion, and that any use is subject to the applicable Beta Services Terms. Salesforce also documents that server URLs and OAuth scopes changed between beta and GA.

Do I need an admin to turn on the Salesforce MCP server first?

Yes. Salesforce's documentation states MCP servers are disabled in your org by default and must be enabled by an administrator before clients can connect, and warns that clients will not connect even with correct authentication if servers are not enabled. An admin activates headless-360 from Setup, and activation can take up to two minutes.

Which OAuth scopes does the Salesforce MCP server require?

Two, mcp_api and refresh_token. The server's own protected-resource descriptor, read on 2026-09-08, names exactly those for this endpoint and points at login.salesforce.com. Salesforce's setup documentation asks for the same pair in the External Client App. There is no read-only scope, so scope choice cannot separate dispatch from dispatch_readonly.

Can I stop the Salesforce MCP connector from changing my org?

Not through OAuth scope, but through three other controls. Salesforce recommends configuring client-level tool permissions so approval is required before a tool changes configuration or deletes data. It also offers scoped read-only servers such as platform/sobject-reads, and notes that External Client Apps can be restricted to specific permission sets.

What rate limits apply to the Salesforce Headless 360 MCP server?

Your org's ordinary API limits. Salesforce documents that catalog-backed tools run as the authenticated user and that the same permissions and rate limits apply as they would to any REST API call made by that user. The connector publishes no separate MCP quota, so a dispatch call is metered against the org's normal API allocation.

Sources

More Sales & CRM connectors

  • Abency

    Run a marketing agency's social, SEO, ads, WordPress and email from an AI agent.

  • Actively

    Read per-account sales intelligence — agent memory, decisions, signals — from an AI agent.

  • Adobe Journey Optimizer

    Inspect campaigns, journeys and channel configurations in Adobe Journey Optimizer from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Salesforce - Beta to work.

Connect Salesforce - Beta once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.