Salesforce Documentation MCP Server
A local-first MCP server that enables intent-based searching across over 350 official Salesforce developer documents and release notes. It allows users to retrieve API references, code examples, and technical documentation directly through natural language queries.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
SalesforceDiariesBySanket
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
search_salesforce_docsSearch Salesforce documentation with relevance-ranked results. Searches across 360 official Salesforce PDF documents including: - Apex Developer Guide & Reference - REST API, SOAP API, Metadata API, Bulk API - Lightning Web Components (LWC) - Visualforce, SOQL/SOSL - Integration patterns, Security g…
get_api_referenceGet specific Salesforce API reference documentation. Supports: REST API, SOAP API, Metadata API, Bulk API 2.0, Tooling API, Streaming API, Chatter REST API, Analytics REST API, and more. Provide the API name and optionally a specific endpoint or resource.
get_release_notesGet Salesforce release notes for specific releases or features. Covers releases from 2015 to present (Winter '26, Summer '25, etc.) Search by release name or by feature keyword.
get_code_exampleGet code examples from Salesforce documentation. Returns code snippets demonstrating specific functionality. Supports: Apex, LWC (JavaScript/HTML), Visualforce, SOQL, Formulas.
list_doc_categoriesList all documentation categories with document counts and descriptions. Useful for understanding what documentation is available.
get_documentGet the full content of a specific Salesforce document by ID or name. Use this after searching to get more detailed content from a specific document.
expand_search_query🧠 LLM-POWERED: Expand a natural language query into optimal search keywords. Use this FIRST when a user asks a vibe-style question that doesn't contain technical terms. This tool analyzes the user's intent and returns: - Expanded technical keywords for searching - Detected Salesforce concepts - Su…
get_document_summariesGet a lightweight catalog of available Salesforce documents. Returns document titles and brief descriptions for the LLM to scan. Use this to understand what documentation is available before searching. Useful for: - Browsing available documentation - Finding the right document when you know the top…
semantic_search_docs🧠 LLM-POWERED: Search with expanded terms for better semantic matching. Use this after expand_search_query to search with both the original query AND expanded keywords. This combines: - Original user query - LLM-generated expanded terms - Category filtering Returns more relevant results for vibe-…
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
9/9 tools missing one or more hints — search_salesforce_docs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_api_reference (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_release_notes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tests exist
No test files found
Add tests that exercise each declared tool.
Secrets not written to files
1 secret value written to files
Avoid persisting secrets to disk. Keep them in memory or your secret manager.
Secrets not logged
2 secret values sent to console.log
Redact or omit secret values from log output.
No arbitrary install scripts
Has postinstall/preinstall script — runs arbitrary code on npm install
Remove postinstall/preinstall hooks unless they’re essential.
Production dependencies are patched
0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.25.2 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/salesforcediariesbysanket/salesforce-docs-mcp)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check