Salesforce Platform MCP Server

Salesforce Hosted MCP Servers are a suite of remote, provider-hosted MCP endpoints that let AI agents (Claude, ChatGPT, Cursor, VS Code, and other MCP clients) securely interact with a Salesforce org. Rather than self-hosting a server, customers enable specific server types in Setup, register an External Client App for OAuth, and connect their MCP client to a URL of the form https://api.salesforce.com/platform/mcp/v1/{servername}. Authentication uses OAuth 2.0 with PKCE, and every tool call executes as the signed-in Salesforce user, so existing CRUD, field-level security, and sharing rules are enforced automatically.

The platform exposes 11 prebuilt server types covering data access (sObject All, Reads, Mutations, Deletes), automation (Invocable Actions, Flows via custom servers), analytics (Tableau Next, Data Cloud queries), and industry clouds (Revenue Cloud, Insurance Cloud, Pricing), plus an API Catalog server for surfacing REST endpoints. Admins can also build custom servers that expose specific Flows, Apex @InvocableMethod classes, and Named Query APIs as MCP tools.

The forcedotcom/mcp-hosted GitHub repo is a community hub and wiki rather than the server source; the servers themselves are hosted by Salesforce. The feature went generally available in April 2026 after a beta starting in October 2025, and requires Enterprise Edition or above.

Tools

Prerequisites

• Salesforce org on Enterprise Edition or above (Developer Edition works for testing)
• Setup/Admin access to enable MCP servers and create External Client Apps
• An MCP-capable client (Claude Desktop, Cursor, VS Code, Postman, etc.)

1. Enable a hosted MCP server

In your Salesforce org, go to Setup → API Catalog → MCP Servers and enable the server type(s) you need, for example platform/sobject-reads for a safe read-only start.

2. Create an External Client App for OAuth

Create an External Client App with:

• Callback URL appropriate for your client (e.g. https://oauth.pstmn.io/v1/callback for Postman)
• OAuth scopes: mcp_api and refresh_token
• PKCE enabled, JWT tokens enabled

Copy the Client ID and Client Secret.

3. Build the server URL

URL pattern depends on the org type:

• Production: https://api.salesforce.com/platform/mcp/v1/{servername}
• Sandbox: https://api.salesforce.com/platform/mcp/v1/sandbox/{servername}
• Scoped to a domain: https://api.salesforce.com/platform/mcp/v1/d/{mydomainname}/{servername}

Replace {servername} with values such as platform/sobject-reads, platform/sobject-all, analytics/tableau-next, etc.

4. Configure your MCP client

Example Claude Desktop / Cursor configuration using a remote MCP entry:

{
  "mcpServers": {
    "salesforce-sobject-reads": {
      "url": "https://api.salesforce.com/platform/mcp/v1/platform/sobject-reads",
      "oauth": {
        "clientId": "YOUR_EXTERNAL_CLIENT_APP_CLIENT_ID",
        "clientSecret": "YOUR_EXTERNAL_CLIENT_APP_CLIENT_SECRET",
        "scopes": ["mcp_api", "refresh_token"]
      }
    }
  }
}

The exact JSON shape varies by client; consult the Connecting Your MCP Client wiki for Claude, Cursor, and VS Code specifics.

5. Verify

Call the getUserInfo tool with no parameters to confirm the connection. A 404 usually means the server is not enabled; a 401 means the OAuth scopes or PKCE setup are not yet propagated (allow up to 30 minutes).

• Let an agent answer pipeline questions over live Salesforce data via platform/sobject-reads without granting any write access.
• Auto-update Opportunity stages, log Tasks, and create Contacts from inbound signals using platform/sobject-all or platform/sobject-mutations.
• Trigger Apex @InvocableMethod automations (lead routing, quote generation, custom scoring) through platform/invocable-actions.
• Run natural-language KPI and dashboard queries on top of Tableau Next semantic models via analytics/tableau-next.
• Pull unified customer profiles and query Data Cloud objects to enrich agent context with Data 360 data.
• Surface a curated set of Flows, Apex actions, and Named Query APIs to an agent via an admin-defined custom server.

• "List the top 10 open Opportunities in the Enterprise segment with close date this quarter, including amount and owner."
• "Create a new Contact at Acme Corp for Jane Doe (jane@acme.com), associate to the Acme account, and add a Task to follow up next Tuesday."
• "Invoke the LeadScoringAction Apex action for every Lead created in the last 24 hours and summarize the scores."
• "Using Tableau Next, show me YoY revenue by region for the last four quarters and explain the biggest movers."
• "Query Data Cloud for unified profiles in the 'High Churn Risk' segment and summarize the top 5 by lifetime value."

• Official, Salesforce-hosted servers with no infrastructure to run or maintain.
• Per-user OAuth 2.0 with PKCE; honors existing CRUD, field-level security, and sharing rules so agents cannot exceed user permissions.
• Broad surface area: 11 prebuilt server types plus custom servers for Flows, Apex actions, and Named Query APIs.
• Granular least-privilege options (separate Reads, Mutations, and Deletes servers) make it safe to scope agent access.

• Requires Enterprise Edition or above and admin work to configure External Client Apps and scopes.
• No free tier; tied to paid Salesforce licensing and the relevant cloud (Tableau Next, Data Cloud, Revenue Cloud) for those servers.
• Each server type is a separate endpoint, so multi-capability workflows may need several MCP connections configured.

• Salesforce DX MCP Server (@salesforce/mcp): official local MCP server focused on Salesforce CLI and developer workflows.
• Community Salesforce MCP servers (various GitHub projects) that wrap the REST/SOQL APIs with a personal access token; less secure than per-user OAuth.
• HubSpot MCP server for teams using HubSpot instead of Salesforce as their CRM.