Salesforce Docs MCP Server

Connect your AI to official company documentation using the Model Context Protocol (MCP).

Overview

The Salesforce Docs MCP Server gives your AI direct access to official Salesforce, MuleSoft, and Tableau documentation. Instead of relying on outdated training data or unstructured web scrapes, your AI can pull directly from the content on these documentation sites:

The benefits of using the Salesforce Docs MCP Server include:

Accuracy: Reduces hallucinations by retrieving directly from structured documentation for precise, grounded answers
Inline access: Query documentation without leaving your IDE or chat window, so you stay focused on building
Freshness: Refreshes from live documentation sites, so content is always current
Security: Accesses only trusted, first-party documentation, avoiding third-party sources or harmful sites
No cost: Requires no API key, no sign-up, and no usage limits

Setup

The Salesforce Docs MCP Server works across any MCP-compatible client.

Run in your terminal:

claude mcp add --transport http salesforce-docs https://mcp.docs.salesforce.com/

Restart Claude Code after adding.

Add to your MCP config file:

Mac/Linux: ~/.cursor/mcp.json
Windows: %USERPROFILE%\.cursor\mcp.json

{
  "mcpServers": {
    "salesforce-docs": {
      "url": "https://mcp.docs.salesforce.com/"
    }
  }
}

Restart Cursor after saving.

Add the server to your OpenCode config:

Global: ~/.config/opencode/opencode.json
Project: opencode.json in your project root

OpenCode also supports .jsonc config files.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "salesforce-docs": {
      "type": "remote",
      "url": "https://mcp.docs.salesforce.com/",
      "enabled": true
    }
  }
}

Restart OpenCode after saving. Run opencode mcp list to confirm that salesforce-docs is connected.

Add to your MCP config file:

Mac/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json

{
  "mcpServers": {
    "salesforce-docs": {
      "serverUrl": "https://mcp.docs.salesforce.com/"
    }
  }
}

Restart Windsurf after saving.

Add to .vscode/mcp.json in your workspace:

{
  "servers": {
    "salesforce-docs": {
      "type": "http",
      "url": "https://mcp.docs.salesforce.com/"
    }
  }
}

Restart VS Code after saving.

Point any MCP-compatible client at:

https://mcp.docs.salesforce.com/

Restart your client after adding.

Verify the Connection

Check your MCP servers. Open your client's MCP server list and confirm that salesforce-docs is there and connected.
Test it. Ask your AI something like, "Using Salesforce documentation, what is Agentforce?".
Look for tool calls. Your client should show that it called salesforce-docs.

Tools

Tool	What it does
`list`	Shows available collections, versions, locales, formats, and how to query them effectively
`list-landmarks`	Shows prominent `guides:` slugs and narrower product areas for one collection, version, and locale
`search`	Finds documents by keyword across a single collection
`fetch`	Retrieves the full content of a document by ID or URL
`answer`	Responds to a natural-language question by searching across a collection, with citations
`explain`	Clarifies a specific document's content by ID or URL

See the Reference for full schemas and examples.

Example Prompts

"What's the difference between Agentforce and Agent Fabric?"
"What are the governor limits for Apex triggers?"
"What languages is the Tableau documentation available in?"
"What guide slugs are available for Tableau documentation in English?"
"What's new in Summer '26 for Agentforce Sales?"
"Retrieve the Salesforce Connect documentation in Markdown."
"How do I create a calculated field in Tableau?"
"Compare the current and previous versions of the DataWeave documentation in MuleSoft."
"Summarize this page: https://help.salesforce.com/s/articleView?id=platform.automate_flow_build_screen_flows_configuring_screens.htm&type=5"

Ask in other languages too. The server auto-detects the language of your question and routes to localized content when available.

Troubleshooting

Problem	Solution
Connection error	Check your internet connection. Try disconnecting and reconnecting.
Tools not showing up	Restart your client. Check your MCP server list to confirm the server is connected. If it's missing, re-add it.
AI not calling the server	Be explicit in your prompt. Try "Using the Salesforce docs MCP server, ..." or "Search the Salesforce documentation for..." You might also need to approve tool permissions on first use.
502 Bad Gateway	The server is likely restarting. Wait a minute and try again.
Unexpected language in results	Call `list` to check the locales supported by the collection, then set `locale` explicitly. If the requested locale isn't available, the server can fall back to `en-us`.
"Document not found" error (`not_found`)	The `fetch` or `explain` tool couldn't find the document by its ID or URL. Verify the ID came from a recent `search` or `answer` result, or check that the URL is a valid documentation page.
"Ambiguous URL" error (`ambiguous_url`)	The URL matches documents in more than one collection, version, or locale. Retry with an explicit `collection`, `version`, and `locale`, or use a result `id` from `search`.
"Slice not available" error (`slice_not_available`)	The requested collection, version, or locale isn't a valid combination. Call `list` to confirm the available slices.
Temporarily shedding load (`admission_shed`)	The server is under load. Wait for the returned `retry_after_seconds` interval, then retry with a smaller request when possible.
Slow first response	This is normal. The first call after connecting requires initialization. Subsequent calls are faster.

Check server status at GET https://mcp.docs.salesforce.com/health.