Enables LLMs to scrape, index, and search modern and legacy Salesforce documentation by piercing complex Shadow DOM and iframe structures. It supports hierarchical spidering of entire guides and local RAG capabilities using a SQLite database for offline querying
Local OnlyTMTrevisan
Awaiting current scanNpm · 1.1.13
The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.
1Distribution channel
5Independently observed tools
0Linked remote endpoints
AvailableVersion intelligence
Detailed security scan evidence is not public for this MCP yet. Public identity, registry metadata, and independently observed protocol inventory remain available.
Install and connect
Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.
Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.
Independent exact-version security scans
Continuous release and vulnerability monitoring
Risk-change alerts with capability context
Historical evidence and API exports
Custom pricingContact salesTailored to your organization, integrations, data needs, and support requirements.
Current version evidence
No public current-version evidence is available yet.
Current protocol inventory
2025-06-18Negotiated protocol
unified-sf-docs-mcpServer-reported name
1Capability groups
Aug 22, 2026Observed
Tools 5
Tool
Category
Annotations
Risk
export_local_documentsExport all matching offline documentation pages concatenated into a single Markdown file on your local machine.Input schema
{
"type": "object",
"properties": {
"outputPath": {
"type": "string",
"description": "Absolute file path to save the .md file."
},
"urlPrefix": {
"type": "string",
"description": "Filter to URLs starting with this."
},
"category": {
"type": "string",
"description": "Filter by category."
}
},
"required": [
"outputPath"
]
}
—
—
mass_extract_guideSpiders a root Salesforce documentation page, extracts hierarchical links, and scrapes them in bulk. Stores contents in a local SQLite database for later searching.Input schema
{
"type": "object",
"properties": {
"rootUrl": {
"type": "string",
"description": "The Table of Contents or landing page."
},
"maxPages": {
"type": "number",
"description": "Maximum number of pages to extract (default 20, max 100)."
},
"category": {
"type": "string"
},
"matchKeyword": {
"type": "string",
"description": "Optional substring. If provided, the crawler will prioritize scraping child links containing this string in their URL."
}
},
"required": [
"rootUrl"
]
}
—
—
read_local_documentRead the full markdown content of a Salesforce documentation page that has already been extracted into the local SQLite database.Input schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "The exact URL of the document to read, obtained from search_local_docs or mass_extract_guide"
}
},
"required": [
"url"
]
}
—
—
scrape_single_pageScrape 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.Input schema
Unified Salesforce Documentation MCP Server questions
How do I install Unified Salesforce Documentation MCP Server?
Install the selected package version with: npm install --save-exact unified-sf-docs-mcp@1.1.13
What tools does Unified Salesforce Documentation MCP Server provide?
Unified Salesforce Documentation MCP Server exposed 5 tools during independent protocol observation, including export_local_documents, mass_extract_guide, read_local_document, scrape_single_page, search_local_docs.
Is Unified Salesforce Documentation MCP Server secure?
The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.
Company and product intelligence
These internal links are derived from strong identity fields such as the implementation name, package, repository, vendor, and listing name—not generic description prose.