Salesforce Metadata MCP logo

Salesforce Metadata MCP

Builds and configures Salesforce metadata, automation, and org components through MCP tools.

Install Salesforce Metadata MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "salesforce-metadata-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "salesforce-metadata-mcp"
      ],
      "env": {
        "SF_INSTANCE_URL": "YOUR_VALUE_HERE",
        "SF_ACCESS_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 20 tools correctly (12d ago).

Overview

salesforce-metadata-mcp MCP server exposes Salesforce org configuration and metadata operations through MCP. It can create and update objects, fields, picklists, layouts, rules, flows, and other components, with read-only schema discovery and dependency analysis. The server runs over stdio and supports on-demand toolsets so clients can access a broad tool catalog without loading every definition at startup. Use it when an agent needs to inspect or modify Salesforce configuration from an MCP-compatible client.

Use cases

  • Create Salesforce custom objects and fields
  • Inspect object schemas before making metadata changes
  • Configure Salesforce flows and approval processes
  • Analyze dependencies before updating fields
  • Load Salesforce toolsets on demand

Key features

  • Salesforce metadata creation and updates
  • Object schema discovery
  • Read-only metadata dependency analysis
  • Flow and automation configuration
  • On-demand MCP toolsets
  • Risk classification for destructive changes

Tools20

What Salesforce Metadata MCP lets your agent do. Expand a tool for its parameters.

Verified live~8.3k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

6/6 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · salesforce-metadata-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads1.7kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed20Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Salesforce Metadata MCP works

What salesforce-metadata-mcp does

salesforce-metadata-mcp connects an MCP client to a Salesforce org for metadata inspection and configuration work. Its advertised catalog contains 228 tools covering object definitions, fields, automation, deployment, Apex, UI components, Agentforce, OmniStudio, DevOps Center, and other Salesforce areas.

Read operations include finding objects by name or label, describing an object’s schema, and checking metadata dependencies. The dependency check is read-only and can identify references to a component and whether a field contains data. Updates to custom objects and fields are risk-classified; destructive field changes report impact before applying them, and object updates use a confirmation gate.

How it works

The server communicates with MCP clients over stdio. It starts with a core selection of tools rather than placing the entire catalog in the model context. Toolsets can be loaded by name, and the server provides meta-tools for searching, listing, loading, invoking, and inspecting tool schemas.

ssf_find_toolsearches the available catalog and loads matching tools.sf_load_toolsetenables a named group, whilesf_list_toolsetsreports available groups and their load state.sf_call_toolcan invoke a tool by name even when that tool is not visible in the client’s current tool list;sf_tool_schemareturns the input schema needed to construct such a call. The default configuration includes core and metadata tools, whileSF_TOOLSETS=allloads the full catalog at startup. A custom comma-separated list can select specific groups such asobjects, flows, automation, or deployment`.

Setup and configuration

Run the package directly with npx -y salesforce-metadata-mcp, or install it globally with npm and launch salesforce-metadata-mcp. A standard MCP configuration supplies the command and passes Salesforce credentials as environment variables:

  • SF_INSTANCE_URL: the Salesforce org URL.
  • SF_ACCESS_TOKEN: the access token used by the server.

Docker is supported; run the container interactively with -i because the stdio connection is driven by the MCP client. The example Docker setup passes the same instance URL and access token variables.

Tools and capabilities

The available examples cover several configuration workflows:

  • Create custom objects, fields, formula fields, metadata types and records, labels, settings, global value sets, record types, business processes, layouts, sharing rules, and field dependencies.
  • Inspect objects and schemas before making changes.
  • Create flows with assignment, decision, record retrieval, record creation, record deletion, and loop elements.
  • Define approval processes, validation rules, workflow field updates, email alerts, assignment rules, escalation rules, auto-response rules, matching rules, and duplicate rules.
  • Create Platform Event objects and analyze metadata dependencies.

The catalog also includes toolsets for areas named in the README, including Agentforce, OmniStudio, DevOps Center, data, Apex, deployment, integrations, monitoring, and reports.

Limitations and notes

Consult the project’s tool documentation for inputs and examples before constructing calls. Client behavior matters when toolsets change: MCP clients are expected to refresh their tool list after a notifications/tools/list_changed event, but clients that do not refresh should use sf_call_tool together with sf_tool_schema.

Flow tools are kept outside the default selection because their schema is comparatively large.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Salesforce Metadata MCP

salesforce-metadata-mcp is an MCP server that connects MCP clients to Salesforce orgs and exposes tools for creating, updating, and inspecting metadata. Its main tools cover objects, fields, formulas, picklists, layouts, flows, rules, schemas, and metadata dependencies, with additional toolsets for broader Salesforce areas.

Install it with `npx -y salesforce-metadata-mcp` or install the npm package globally and run `salesforce-metadata-mcp`. Configure the MCP client with `SF_INSTANCE_URL` and `SF_ACCESS_TOKEN`. Docker and a Claude Desktop extension bundle are also documented.

It describes the server as usable with Claude or any MCP client and communicates over stdio, but it does not document Cursor-specific setup or compatibility details.

Set `SF_TOOLSETS` to `none`, `all`, or a comma-separated selection such as `metadata,objects,automation,security`. The server can also load toolsets on demand with its meta-tools, while `sf_call_tool` and `sf_tool_schema` provide access when a client does not refresh its tool list.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSalesforce Metadata MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/salesforce-metadata-mcp?style=directory)](https://allmcps.com/mcp/salesforce-metadata-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/salesforce-metadata-mcp"><img src="https://allmcps.com/api/badge/salesforce-metadata-mcp?style=directory" alt="Salesforce Metadata MCP on AllMCPs" /></a>