Salesforce Metadata MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 584 installs a week from npm. Last commit 21 Oct 2026.
The only Salesforce MCP with Agentforce, OmniStudio & DevOps Center tools — 228 total.
What the code does
We read the source, 7 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const output = execSync(
`/query?q=${encodeURIComponent(`SELECT COUNT() FROM ${obj}`)}`
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add salesforce-metadata-mcp -e 'SF_INSTANCE_URL=<SF_INSTANCE_URL>' -- npx -y salesforce-metadata-mcp{
"mcpServers": {
"salesforce-metadata-mcp": {
"command": "npx",
"args": [
"-y",
"salesforce-metadata-mcp"
],
"env": {
"SF_INSTANCE_URL": "<SF_INSTANCE_URL>"
}
}
}
}[mcp_servers.salesforce-metadata-mcp]
command = "npx"
args = ["-y", "salesforce-metadata-mcp"]
env = { SF_INSTANCE_URL = "<SF_INSTANCE_URL>" }{
"mcpServers": {
"salesforce-metadata-mcp": {
"command": "npx",
"args": [
"-y",
"salesforce-metadata-mcp"
],
"env": {
"SF_INSTANCE_URL": "<SF_INSTANCE_URL>"
}
}
}
}{
"servers": {
"salesforce-metadata-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"salesforce-metadata-mcp"
],
"env": {
"SF_INSTANCE_URL": "<SF_INSTANCE_URL>"
}
}
}
}Put your own value in place of
<SF_INSTANCE_URL> (Salesforce org URL, e.g. https://yourorg.my.salesforce.com).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
SF_ACCESS_TOKEN (Salesforce access token (or use SF_ALIAS / JWT variables instead)), SF_ALIAS (Salesforce CLI org alias (alternative to SF_ACCESS_TOKEN)), SF_TOOLSETS (Toolsets to load at startup: 'all', 'none', or a comma-separated list. Default: core,metadata. All 228 tools stay available via sf_find_tool / sf_load_toolset, and callable via sf_call_tool even on clients that do not refresh their tool list), SF_PRODUCTION_GUARD (Refuse destructive tools on production orgs: 'destructive' (default), 'strict', or 'off'. Metadata creation is never affected).
Alternatives to Salesforce Metadata MCP
same job, measured the same way13 rules on a Salesforce Agentforce topic file, before the deploy and before Article 50
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
mtdt.io MCP: Salesforce DevOps platform connector (metadata deployments, backups and more)
mtdt.io MCP: Salesforce DevOps platform connector (metadata deployments, backups and more)
Deploy web apps via AI agents with sota.io. 9 tools for deploy, logs, env, and more.
AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 31 MCP tools.
Enterprise-grade MySQL MCP Server with OAuth 2.0, 106 tools, and Docker deployment
AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 61 MCP tools.
Salesforce Metadata MCP — questions
Answers built from our own checks of this server.