Developer · Local MCP server
Salesforce Metadata MCP
The only Salesforce MCP with Agentforce, OmniStudio & DevOps Center tools - 228 total.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.semwalajay83-sem/salesforce-metadata-mcp- Version
- 3.2.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- semwalajay83-sem (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/semwalajay83-sem) · how
- Listed under
- Salesforce MCP servers
- Repository
- github.com/semwalajay83-sem/salesforce-metadata-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | salesforce-metadata-mcp | 3.2.0 | stdio |
How to connect Salesforce Metadata MCP
Salesforce Metadata MCP runs locally from a Node.js package published to the npm registry: salesforce-metadata-mcp version 3.2.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y salesforce-metadata-mcp@3.2.0. It reads these environment variables: SF_INSTANCE_URL (required), SF_ACCESS_TOKEN (secret), SF_ALIAS, SF_TOOLSETS and SF_PRODUCTION_GUARD; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"salesforce-metadata-mcp": {
"command": "npx",
"args": [
"-y",
"salesforce-metadata-mcp@3.2.0"
],
"env": {
"SF_INSTANCE_URL": "<value>",
"SF_ACCESS_TOKEN": "<secret>",
"SF_ALIAS": "<value>",
"SF_TOOLSETS": "<value>",
"SF_PRODUCTION_GUARD": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| SageMathStateful SageMath MCP server with 40 tools and a sandboxed Sage session per client. | Local · stdio |
| Sagemath MCP ServerMCP server wrapping SageMath's full computer algebra system - 10 symbolic-math tools for LLMs. | Local · stdio |
| Salesforce CloudAI-powered Salesforce CRM: opportunity intelligence, conversation analysis, SOQL, analytics. | Local · stdio |
| Salesforce DevopsPlan Salesforce deploys, open pull requests and trigger pipelines from your AI client. | Remote · HTTPLive check: sign-in required |
| SAME - Stateless Agent Memory EnginePersistent memory for AI coding agents. Local-first SQLite + vector search. 17 MCP tools. | Local · stdio |
| Samotpravil MCPMCP server for Samotpravil API - docs, typed tools, Python SDK parity, safety flags. | Local · stdio |
| SampuliFormat-true synthetic test data for 90 countries - IBANs, SWIFT/BIC, IDs, cards, all certified. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| SandBaseConnect MCP clients to 2,000+ AI models without managing provider API keys. | Remote · HTTPLive check: sign-in required |