Salesforce Metadata MCP Server

by semwalajay83-semio.github.semwalajay83-sem/salesforce-metadata-mcpv3.2.0

The only Salesforce MCP with Agentforce, OmniStudio & DevOps Center tools — 228 total.

2Node.jsstdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Active8d ago

Install Salesforce Metadata MCP server

claude mcp add salesforce-metadata -e SF_INSTANCE_URL='<sf-instance-url>' -e SF_ACCESS_TOKEN='<sf-access-token>' -- npx -y salesforce-metadata-mcp

{
  "mcpServers": {
    "salesforce-metadata": {
      "command": "npx",
      "args": [
        "-y",
        "salesforce-metadata-mcp"
      ],
      "env": {
        "SF_INSTANCE_URL": "<sf-instance-url>",
        "SF_ACCESS_TOKEN": "<sf-access-token>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).

{
  "mcpServers": {
    "salesforce-metadata": {
      "command": "npx",
      "args": [
        "-y",
        "salesforce-metadata-mcp"
      ],
      "env": {
        "SF_INSTANCE_URL": "<sf-instance-url>",
        "SF_ACCESS_TOKEN": "<sf-access-token>"
      }
    }
  }
}

Settings → Developer → Edit Config (claude_desktop_config.json), then restart.

{
  "servers": {
    "salesforce-metadata": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "salesforce-metadata-mcp"
      ],
      "env": {
        "SF_INSTANCE_URL": "<sf-instance-url>",
        "SF_ACCESS_TOKEN": "<sf-access-token>"
      }
    }
  }
}

Add to .vscode/mcp.json in your workspace.

{
  "mcpServers": {
    "salesforce-metadata": {
      "command": "npx",
      "args": [
        "-y",
        "salesforce-metadata-mcp"
      ],
      "env": {
        "SF_INSTANCE_URL": "<sf-instance-url>",
        "SF_ACCESS_TOKEN": "<sf-access-token>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json.

Configuration

Variable	Required	Secret	Description
SF_INSTANCE_URL	yes	—	Salesforce org URL, e.g. https://yourorg.my.salesforce.com
SF_ACCESS_TOKEN	—	yes	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.

Freshness

Active — last maintenance signal 8d ago. The newest of the signals below sets the band.

Last commit (default branch)
2026-10-01 · 8d ago · GitHub
Latest release
2026-09-23 · 16d ago · GitHub · v3.2.0
Package published
no data · npm/PyPI
Registry entry updated
2026-09-30 · 9d ago · official registry · v3.2.0

FAQ

›How do I install the Salesforce Metadata MCP server in Claude Code?

Run: claude mcp add salesforce-metadata -e SF_INSTANCE_URL='<sf-instance-url>' -e SF_ACCESS_TOKEN='<sf-access-token>' -- npx -y salesforce-metadata-mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Salesforce Metadata require an API key?

Yes. It expects SF_INSTANCE_URL, SF_ACCESS_TOKEN, of which 1 is a secret.

›Can I use Salesforce Metadata as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is Salesforce Metadata in the official MCP registry?

Yes, as io.github.semwalajay83-sem/salesforce-metadata-mcp.