Unified Salesforce Documentation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrape_single_pageA | Scrape a single Salesforce documentation page. Returns markdown. If you do not know the exact URL, you should first use a Web Search tool (like Brave or DuckDuckGo) to search for 'site:developer.salesforce.com/docs [topic]' or 'site:help.salesforce.com [topic]', then pass the retrieved URL here. |
| mass_extract_guideA | Spiders a root Salesforce documentation page, extracts hierarchical links, and scrapes them in bulk. Stores contents in a local SQLite database for later searching. |
| search_local_docsC | Search locally extracted Salesforce documentation in the SQLite database. |
| read_local_documentA | Read the full markdown content of a Salesforce documentation page that has already been extracted into the local SQLite database. |
| export_local_documentsA | Export all matching offline documentation pages concatenated into a single Markdown file on your local machine. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Tools have distinct purposes, but there is slight overlap between 'export_local_documents' and 'mass_extract_guide', as both involve extracting documentation content. Descriptions help differentiate, but an agent might be uncertain which to use for a given task.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., export_local_documents, search_local_docs), making it predictable and easy to understand.
Five tools cover the core operations for Salesforce documentation (extraction, reading, searching, export) without being excessive or sparse, fitting the server's purpose well.
The tool set covers essential documentation workflows: bulk/single extraction, reading, searching, and export. A minor gap is the lack of a tool to list all available documents in the local database, but agents can work around this using search.