salesforce

This Salesforce MCP Server provides a comprehensive set of MCP tools to interact with Salesforce data and metadata. It exposes 17 tools across categories such as Query & Search (execute-soql, execute-sosl, describe-sobject), Apex Development (execute-apex, run-apex-tests, get-apex-logs), Data Management (create-record, get-record, update-record, delete-record, upsert-record), Metadata (list-metadata-types, deploy-metadata, deploy-bundle, retrieve-metadata, check-deploy-status), and Connection (test-connection). The server supports dual authentication (Username/Password and OAuth2) and includes smart caching, auto-bulk switching, and thorough logging for debugging. Use the client tools you rely on (Claude Desktop, Cline, Cursor, or other MCP-compatible clients) to issue commands like executing SOQL, retrieving records, deploying metadata, or validating connections. Configure the MCP server in your client’s settings with the appropriate credentials and ensure the requested operations are allowed by your environment.

Prerequisites:

• Node.js and npm/yarn installed on your machine
• Access to install npm packages from the public registry

Installation steps:

1. Ensure Node.js is installed. You can verify with: node -v npm -v

2. Install or run via npx the Salesforce MCP Server package from the MCP configuration: npx -y @jjar/salesforce-mcp-server // This will start the MCP server using the configured options in your MCP client config

3. If you are wiring this into an MCP configuration file, reference the following example in your client: { "mcp.servers": { "salesforce": { "command": "npx", "args": ["-y", "@jjar/salesforce-mcp-server"], "env": { "SF_USERNAME": "your-username@company.com", "SF_PASSWORD": "your-password", "SF_SECURITY_TOKEN": "", "SF_LOGIN_URL": "https://login.salesforce.com" }, "disabled": false, "alwaysAllow": ["test-connection", "execute-soql", "describe-sobject", "get-record", "get-apex-logs", "list-metadata-types"] } } }

4. Restart your MCP client or editor after updating the configuration to apply changes.

Tips and considerations:

• Use the alwaysAllow list to grant only the safe, read-only operations by default; add modification operations (create-record, update-record, delete-record, upsert-record) only if you fully trust the client and user workflow.
• For OAuth2, ensure you have a connected app configured in Salesforce and supply SF_CLIENT_ID, SF_CLIENT_SECRET, and a refresh token as appropriate.
• The system supports dual authentication paths (Username/Password and OAuth2) with a flexible SF_INSTANCE_URL depending on production or sandbox environments.
• The caching layer for SObject metadata uses a 1-hour TTL; consider adjusting if your org schema changes frequently.
• If you encounter connection errors, double-check the SF_LOGIN_URL, credentials, and network access from your hosting machine to Salesforce endpoints.
• After editing MCP server settings in an editor, restart the MCP client to ensure changes take effect.