SkillAgentSearch skills...

salesforce-metadata-mcp

MCP server with 228 tools for Salesforce: metadata, flows, Apex, LWC, Agentforce, OmniStudio, reports, permissions, impact analysis and more. Manage your org from Claude in natural language.

Install / Use

claude mcp add semwalajay83-sem -- npx -y github:semwalajay83-sem/salesforce-metadata-mcp

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

83/100

Category

Sales

Supported Platforms

Claude Code
Claude Desktop

Tags

Our assessment of salesforce-metadata-mcp

salesforce-metadata-mcp scores 83/100 on our quality scale, 40th of 46 Sales skills we index.

Its MCP Server is 18 KB long, well organised into 25 sections with 6 code examples: a thorough specification that gives an agent plenty to work with.

It has 3 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
3/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 29 days ago, so salesforce-metadata-mcp is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

salesforce-metadata-mcp compared with similar skills

All 4 of these similar skills score higher than salesforce-metadata-mcp; compare them before choosing.

SkillScoreStarsUpdatedFormat
salesforce-metadata-mcp (this skill)by semwalajay83-sem83329d agoMCP Server
Agent-Reachby Panniantong100113.3k12d agoCLAUDE.md
hyperframesby heygen-com10087.1ktodayCLAUDE.md
rufloby ruvnet10082.1ktodayCLAUDE.md
headroomby headroomlabs-ai10080.2ktodayCLAUDE.md

Frequently asked questions

How do I install salesforce-metadata-mcp?
Run claude mcp add semwalajay83-sem -- npx -y github:semwalajay83-sem/salesforce-metadata-mcp. The install tabs above show the steps for each supported agent.
Which AI agents does salesforce-metadata-mcp work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is salesforce-metadata-mcp safe to use?
It is MIT-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is salesforce-metadata-mcp still maintained?
The repository was last updated 29 days ago, so salesforce-metadata-mcp is actively maintained.

salesforce-metadata-mcp

npm version npm downloads License: MIT MCP Compatible

The only Salesforce MCP server that builds Agentforce agents, OmniStudio components, and DevOps Center pipelines — alongside a complete daily developer loop (schema describe, Apex read, debug logs) and 228 tools total for building, configuring, and automating Salesforce orgs directly from Claude or any MCP client.


Quick Start

npx -y salesforce-metadata-mcp

Or install globally:

npm install -g salesforce-metadata-mcp
salesforce-metadata-mcp

Configuration (Claude Desktop / Claude Code)

Add to your MCP configuration (claude_desktop_config.json or .claude/settings.json):

{
  "mcpServers": {
    "salesforce": {
      "command": "npx",
      "args": ["salesforce-metadata-mcp"],
      "env": {
        "SF_INSTANCE_URL": "https://your-org.salesforce.com",
        "SF_ACCESS_TOKEN": "your_access_token"
      }
    }
  }
}

See SETUP.md for all authentication methods and detailed setup instructions.

One-click install (Claude Desktop)

Download salesforce-metadata-mcp-<version>.mcpb from the latest release, then drag it into Claude Desktop → Settings → Extensions. It prompts for your org URL and credentials — no JSON editing.

The bundle resolves the server from npm at launch rather than embedding a copy, so it always runs the current published version and never needs re-downloading after an upgrade.

Docker

docker build -t salesforce-metadata-mcp .
docker run -i --rm \
  -e SF_INSTANCE_URL="https://your-org.my.salesforce.com" \
  -e SF_ACCESS_TOKEN="your_access_token" \
  salesforce-metadata-mcp

The image builds from source, runs as a non-root user, and ships production dependencies only. Because this server speaks MCP over stdio, -i is required — the container is driven by its client, not run as a background service. SF_ALIAS will not work in a container: the Salesforce CLI's login flow needs a browser, so use token, JWT, refresh-token, or client-credentials variables instead.


Toolsets — loading 228 tools without burning your context

All 228 tools are always available. Most are not loaded into the model's context until something asks for them.

Listing every tool up front costs roughly 98,000 tokens — about half a 200k context window, spent before you type anything, whether or not the session ever touches OmniStudio or DevOps Center. A 228-candidate tool list also makes the model measurably worse at picking the right tool. So the server starts with a small core loaded and pulls in the rest on demand:

| Startup | Tools listed | Approx. tokens | |---------|-------------:|---------------:| | Default (core,metadata) | 20 | ~9,900 | | After loading two more toolsets | 43 | ~20,800 | | SF_TOOLSETS=all | 233 | ~99,100 |

The default covers what nearly every session needs: describe/list objects, SOQL query, deploy/retrieve/delete metadata, deploy status, and core schema creation (objects, fields, formula fields, picklist values, validation rules, approval processes).

Five tools are always present and make everything else reachable:

  • sf_find_tool — search all 228 tools by name and load whatever contains the matches, in one call. Ask for "create an omniscript" and it finds the tools, loads omnistudio, and they are callable immediately. This is usually all you or the model needs.
  • sf_load_toolset — load named toolsets explicitly.
  • sf_list_toolsets — browse all toolsets, their tool counts, and what is loaded.
  • sf_call_tool — invoke any tool by name, loaded or not, without it having to appear in the tool list first. Arguments are validated and the production guard applies exactly as on a direct call.
  • sf_tool_schema — return any tool's input schema, so sf_call_tool can be constructed for a tool the client cannot see.

In practice you don't manage this by hand: ask for what you want, and the model loads what it needs.

If loaded tools don't show up

Loading a toolset enables it on the server and emits notifications/tools/list_changed. A client is supposed to re-fetch tools/list when it sees that. Some clients don't — and when that happens, the load reports success, the tools really are enabled, and the model still cannot call any of them because they never entered its tool list.

Two things handle this, so no client can lose access to a tool:

  • sf_load_toolset checks whether the client re-fetched and says so in its response, instead of reporting an unqualified success for tools that have become unreachable.
  • sf_call_tool reaches every tool without needing a re-fetch at all. Combined with sf_tool_schema, the full 228-tool surface is usable from the handshake tool list alone — even under SF_TOOLSETS=none.

To restore the previous behaviour of loading everything at startup, set SF_TOOLSETS=all. To start with only the five meta-tools, set SF_TOOLSETS=none. To pick your own core, pass a list:

{ "env": { "SF_TOOLSETS": "metadata,objects,automation,security" } }

Available toolsets: core, metadata, objects, data, flows, automation, security, apex, lwc, ui, pages, actions, agentforce, omnistudio, omnichannel, devops, deployment, integrations, identity, reports, experience, admin, monitoring, audit, einstein, knowledge, cpq, sandbox, streaming, visualforce, aura, comms, mcp, i18n.

Flow tools live in their own flows toolset because sf_create_flow carries the full Flow element schema — 15,266 bytes (~4,126 tokens) on its own, the largest tool definition in the server. Keeping it out of the default means sessions that never build a Flow never pay for it, while sessions that do still get the complete validated schema.


Tools — 228 total

Highlights below; see TOOLS.md for the complete reference with parameters and example prompts.

Objects & Fields

| Tool | Description | |------|-------------| | sf_create_custom_object | Create a custom object with all settings | | sf_create_custom_field | Create a field on any object (all types) | | sf_create_formula_field | Create formula fields with full formula language support | | sf_add_picklist_values | Add values to existing picklist fields | | sf_create_custom_metadata_type | Create a Custom Metadata Type (__mdt) | | sf_create_custom_metadata_record | Create records for a Custom Metadata Type | | sf_create_custom_label | Create or update Custom Labels | | sf_create_custom_setting | Create Hierarchy or List Custom Settings | | sf_create_global_value_set | Create shared picklist usable across objects | | sf_create_record_type | Create Record Types with picklist overrides | | sf_create_business_process | Create Business Processes for Opp/Lead/Case | | sf_create_page_layout | Create Page Layouts with sections and fields | | sf_create_sharing_rule | Create criteria or ownership sharing rules | | sf_create_field_dependency | Create controlling/dependent picklist dependency | | sf_describe_object | Read an object's full schema — fields, types, picklist values, child relationships, record types | | sf_list_objects | Find objects by partial name or label — the discovery step before sf_describe_object | | sf_get_metadata_dependencies | Impact analysis: what references this component, and does the field hold data? Read-only | | sf_update_custom_object | Update object-level properties, risk-classified with a confirmation gate | | sf_update_custom_field | Update a field's definition, risk-classified — destructive changes report impact before applying |

Automation

| Tool | Description | |------|-------------| | sf_create_flow | Create any Flow type — Assignment, Decision, GetRecords, CreateRecords (with field values), DeleteRecords, Loop | | sf_create_approval_process | Create multi-step approval processes | | sf_create_validation_rule | Create data validation rules | | sf_create_workflow_field_update | Create workflow field update actions | | sf_create_email_alert | Create workflow email alert actions | | sf_create_platform_event | Create Platform Event objects | | sf_create_assignment_rule | Create Lead/Case assignment rules | | sf_create_escalation_rule | Create Case escalation rules | | sf_create_auto_response_rule | Create Web-to-Lead/Case auto-response rules | | sf_create_matching_rule | Create duplicate matching rules | | sf_create_duplicate_rule | Create duplicate detection rules | | sf_create_apex_email_service | Create inbound Apex email services | | sf_create_scheduled_job | Schedule an Apex class via cron |

Security & Access

| Tool | Description | |------|-------------| | sf_create_permission_set | Create Permission Sets with all permissions | | sf_create_role | Create roles in the role hierarchy | | sf_create_queue | Create queues with members and objects | | sf_create_named_credential | Create Named Credentials for callouts | | sf_get_field_permissions | Audit current field-level security grants across Profiles and Permission Sets |

UI & Experience

| Tool | Description | |------|-------------| | sf_create_lightning_app | Create Lightning Apps with nav/utility bars | | sf_create_tab | Create Custom Tabs for objects | | sf_create_compact_layout | Create Compact Layouts (highlights panel) | | sf_create_list_view | Create List Views with filters and columns | | sf_create_email_template | Create HTML/text email templates | | sf_create_static_resource | Create Static Resources from text content | | sf_create_custom_notification_type | Create Custom Notification Types | | sf_create_report_type | Create Custom Report Types | | sf_create_dashboard | Create Dashboards with components |

Apex Development

| Tool | Description | |------|-------------| | sf_create_apex_class | Deploy any Apex class to the org | | sf_create_apex_trigger | Deploy an Apex trigger on any object | | sf_create_apex_test_class | Deploy test classes, optionally run tests | | sf_run_apex_tests | Run test classes and get pass/fail results | | sf_execute_anonymous_apex | Execute anonymous Apex and see output | | sf_get_apex_class | Read the source of an existing Apex class | | sf_get_apex_trigger | Read the source of an existing Apex trigger | | sf_enable_debug_logs | Turn on Apex debug logging for a user (TraceFlag) | | sf_disable_debug_logs | Turn Apex debug logging back off (deletes active TraceFlags) | | sf_get_debug_logs | List recent Apex debug logs | | sf_get_debug_log_body | Read the full content of a debug log | | sf_scan_apex_antipatterns | Lightweight heuristic scan for SOQL/DML-in-loop, hardcoded IDs, debug statements | | sf_run_code_scanner | Multi-engine static analysis (PMD, SFGE SOQL-injection data-flow, RetireJS, ESLint) via Salesforce Code Analyzer |

LWC Development

| Tool | Description | |------|-------------| | sf_create_lwc | Deploy a full LWC with HTML, JS, CSS | | sf_update_lwc | Update an existing LWC component |

Experience Cloud

| Tool | Description | |------|-------------| | sf_create_experience_site | Create Experience Cloud sites | | sf_create_experience_page | Create pages within Experience sites |

Agentforce

| Tool | Description | |------|-------------| | sf_create_agent | Create Agentforce Agent (Bot shell) | | sf_create_agent_action | Create Ag

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars3
CategorySales
Updated29d ago
Forks0

Languages

TypeScript

Trust signals

92/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 low