@salesforce/mcp

What it does

This MCP server connects Claude and other LLMs to Salesforce orgs, enabling read and write access to org metadata, data, users, and administrative functions. It exposes Apex test execution, metadata queries and updates, data manipulation, and org configuration tools. Configuration is granular: you specify target orgs via the --orgs flag, which toolsets to enable (orgs, metadata, data, users), and optionally which individual tools to expose. The server is maintained by Salesforce, currently in beta, with comprehensive documentation in the Salesforce DX Developer Guide.

Who it's for

Salesforce developers and admins using Claude Code, Cursor, or Cline to automate org management; backend engineers wiring LLMs into Salesforce deployments or CI/CD pipelines; teams building AI-assisted configuration and migration tools.

Common use cases

• Execute and analyze Apex tests through natural language prompts
• Query and modify org metadata (custom objects, fields, Apex classes) via Claude
• Automate data migrations and bulk operations by describing them to the LLM
• Manage user accounts, permissions, and org-wide settings interactively

Setup pitfalls

• Beta service — subject to Salesforce Beta Services Terms; feature or API changes may occur
• Requires explicit JSON configuration in your MCP client (.mcp.json for Claude Code, cline_mcp_settings.json for Cline, etc.) with --orgs, --toolsets, and --tools flags; no auto-discovery
• Depends on local Salesforce DX CLI authentication and org context — the server makes no network calls itself, so your authenticated sfdx environment is mandatory
• Requires filesystem read/write access to org metadata and state files; ensure your MCP client sandbox permits this