Salesforce Docs MCP

Programmatic access to Salesforce Customer Experience documentation for AI agents, via the Model Context Protocol.

Endpoint

This server speaks MCP over HTTP using the Streamable HTTP transport.

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

Also reachable at https://docs.salesforce.com/mcp/ (the same server, path-namespaced). Health: GET /health — Online docs: GET /about/ (you are here).

Collections

One server, six documentation collections. Each tool operates over a single slice — a (collection, version, locale) triple.

Collection	Covers	Versions / Locales	Notable
`tableau`	Tableau Desktop, Server, Cloud, Prep, Public, Mobile, Reader, the developer APIs, Blueprint	`current` + `next` (release preview); 15 locales: de-de, en-gb, en-us, es-es, fr-ca, fr-fr, it-it, ja-jp, ko-kr, nl-nl, pt-br, sv-se, th-th, zh-cn, zh-tw	text / markdown / html bodies
`admin`	Salesforce admin & end-user help across the product line (Sales, Service, Marketing, Commerce, industry clouds, Platform, Agentforce, Data 360…)	`current`; en-us	`+release:` quarterly-release filter
`mulesoft`	MuleSoft / Anypoint connectors, runtime, DataWeave	`current`; en-us, ja-jp	`+release:` per-component version filter
`developer`	Salesforce developer guides & references (Marketing Cloud, AMPscript, LWC…)	`current`; en-us	guide vs reference doc types
`architect`	Well-Architected guidance and decision frameworks	`current`; 10 locales: de-de, en-us, es-mx, fr-fr, it-it, ja-jp, ko-kr, pt-br, zh-cn, zh-tw	`+pill:new` / `+updated:` recency facet
`legacydeveloper`	Salesforce platform developer reference (Atlas): Apex, SOAP/REST APIs, object & field reference	`current`; en-us	deprecating — migrating into `developer`

Every collection exposes the same product-scoping idiom: a guides:<slug> filter in search.query — used as a bare boost to expand (the default) or with a leading + to hard-scope to one product. Call list for the live catalog (each collection's exact versions, locales, body formats, slug vocabulary in retrievalHints, and landmarks); the rows above are a snapshot.

Localized, not just English

This is built to be multilingual, not en-us-only: Tableau ships 15 locales and Architect 10, and the broader Salesforce documentation set is about 90% non-English at source — so localized coverage grows as more of it is indexed. Search and answer ground in the language you ask in: leave locale at its default "auto" and the server detects the question's language and routes to that locale's slice when the collection has it, answering from the localized source rather than translating English. Or target a locale explicitly (e.g. "ja-jp"). Coverage varies by collection — some are en-us-only today; see each collection's locales[] from list for exactly what it carries.

Tools

Five tools are exposed. See the API reference for full schemas, and examples for copy-pasteable JSON-RPC.

Tool	Purpose
`list`	Catalog of collections, versions, locales, formats, retrieval hints, landmarks, and sampled extra fields.
`search`	Ranked retrieval over a single collection/version/locale slice.
`fetch`	Direct lookup of documents by id or url.
`answer`	Synthesized answer grounded in retrieved documents, with citations.
`explain`	Synthesized answer grounded in one specific document (by id or url).

Pointing your client

Most MCP clients accept a Streamable HTTP endpoint. Configure yours with:

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

The path-namespaced form https://docs.salesforce.com/mcp/ reaches the same server. Use a trailing slash either way — some clients fail to connect without it.