Salesforce MCP

What is MCP Salesforce Connector?

MCP Salesforce Connector is a server implementation of the Model Context Protocol (MCP) that facilitates the integration of Large Language Models (LLMs) with Salesforce. It allows LLMs to interact with Salesforce data and metadata by executing SOQL queries, SOSL searches, and various other Salesforce API requests.

How to use MCP Salesforce Connector?

To use MCP Salesforce Connector, you need to configure it within your claude_desktop_config.json file. Add an entry to the mcpServers section, specifying the command and arguments for the connector. Authentication can be done via OAuth (recommended, by setting SALESFORCE_ACCESS_TOKEN and SALESFORCE_INSTANCE_URL as environment variables) or Username/Password (legacy method, using SALESFORCE_USERNAME, SALESFORCE_PASSWORD, and SALESFORCE_SECURITY_TOKEN).

Key Features of MCP Salesforce Connector

• Execute SOQL (Salesforce Object Query Language) queries: Retrieve specific data from Salesforce objects.
• Perform SOSL (Salesforce Object Search Language) searches: Conduct text-based searches across multiple Salesforce objects.
• Retrieve metadata for Salesforce objects: Access information about object fields, labels, and types.
• Retrieve, create, update, and delete records: Perform standard CRUD operations on Salesforce records.
• Execute Tooling API requests: Interact with Salesforce metadata and develop custom tools.
• Execute Apex REST requests: Call custom Apex REST services.
• Make direct REST API calls to Salesforce: Execute any valid Salesforce REST API request.

Use Cases of MCP Salesforce Connector

• AI-powered CRM interactions: Enable LLMs to directly query and manipulate Salesforce data for customer service, sales, and marketing automation.
• Automated data retrieval and reporting: Generate reports and extract insights from Salesforce using natural language queries.
• Custom Salesforce integrations: Develop bespoke applications that leverage LLMs to interact with Salesforce in novel ways.
• Enhanced data management: Automate data entry, updates, and deletions within Salesforce through LLM commands.

FAQ about MCP Salesforce Connector

Q: What authentication methods are supported? A: The server supports OAuth (recommended) and Username/Password (legacy) authentication methods.

Q: Do I need to set up both OAuth and Username/Password authentication? A: No, if OAuth environment variables (SALESFORCE_ACCESS_TOKEN and SALESFORCE_INSTANCE_URL) are not set, the server will fall back to Username/Password authentication.

Q: Can I use this connector with any LLM? A: This connector is designed to work with LLMs that support the Model Context Protocol (MCP).

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",
            }
        }
    }
}

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.