MCP Salesforce Connector

MCP Salesforce Connector

What is MCP Salesforce Connector about?

Provides a Model Context Protocol (MCP) server that bridges large language models with Salesforce, allowing programmatic execution of SOQL, SOSL, Tooling API, Apex REST, and generic REST requests.

How to use MCP Salesforce Connector?

1. Add an entry to the claude_desktop_config.json under mcpServers using the provided configuration.
2. Supply required environment variables for authentication (OAuth token or username/password).
3. Invoke the server via the specified command (e.g., uvx --from mcp-salesforce-connector salesforce).
4. Issue MCP‑formatted requests from your LLM application to execute queries, retrieve metadata, or perform CRUD operations on Salesforce objects.

Key features of MCP Salesforce Connector

• Execute SOQL queries and SOSL searches.
• Retrieve object metadata (field names, labels, types).
• Create, read, update, and delete Salesforce records.
• Access the Tooling API and Apex REST endpoints.
• Perform arbitrary REST API calls to any Salesforce endpoint.
• Supports OAuth (recommended) and legacy username/password authentication.
• Optional sandbox connection via SALESFORCE_DOMAIN= test.

Use cases of MCP Salesforce Connector

• Automating data extraction for reporting or analytics.
• Enabling conversational agents to fetch or modify CRM records on‑the‑fly.
• Building AI‑assisted admin tools for Salesforce object inspection and management.
• Integrating LLM‑driven workflows with existing Salesforce processes (e.g., lead qualification, case updates).

FAQ from the MCP Salesforce Connector

Q: Which authentication method should I use? A: OAuth is recommended; set SALESFORCE_ACCESS_TOKEN and SALESFORCE_INSTANCE_URL. The server falls back to username/password if those are absent.

Q: How do I connect to a sandbox environment? A: Set SALESFORCE_DOMAIN to test.

Q: Can I call custom Apex REST endpoints? A: Yes, use the Apex REST request feature to target any custom endpoint.

Q: What if I need to execute a non‑standard REST call? A: The direct REST API capability lets you specify method, URL, headers, and body.

MCP Salesforce Connector

A Model Context Protocol (MCP) server implementation for Salesforce integration, allowing LLMs to interact with Salesforce data through SOQL queries and SOSL searches.

Features

• Execute SOQL (Salesforce Object Query Language) queries
• Perform SOSL (Salesforce Object Search Language) searches
• Retrieve metadata for Salesforce objects, including field names, labels, and types
• Retrieve, create, update, and delete records
• Execute Tooling API requests
• Execute Apex REST requests
• Make direct REST API calls to Salesforce

Configuration

Model Context Protocol

To use this server with the Model Context Protocol, you need to configure it in your claude_desktop_config.json file. Add the following entry to the mcpServers section:

{
    "mcpServers": {
        "salesforce": {
        "command": "uvx",
        "args": [
            "--from",
            "mcp-salesforce-connector",
            "salesforce"
        ],
        "env": {
            "SALESFORCE_ACCESS_TOKEN": "SALESFORCE_ACCESS_TOKEN",
            "SALESFORCE_INSTANCE_URL": "SALESFORCE_INSTANCE_URL",
            "SALESFORCE_DOMAIN": "SALESFORCE_DOMAIN"
            }
        }
    }
}

Note on Salesforce Authentication Methods

This server supports two authentication methods:

• OAuth (Recommended): Set SALESFORCE_ACCESS_TOKEN and SALESFORCE_INSTANCE_URL as environment variables.
• Username/Password (Legacy): If SALESFORCE_ACCESS_TOKEN and SALESFORCE_INSTANCE_URL are not set, the server will fall back to using SALESFORCE_USERNAME, SALESFORCE_PASSWORD, and SALESFORCE_SECURITY_TOKEN.

Environment Configuration

• SALESFORCE_DOMAIN (Optional): Set to test to connect to a Salesforce sandbox environment. If not set or left empty, the server will connect to the production environment.