Skip to main content
Glama
ampcome-mcps

MCP Salesforce Connector

by ampcome-mcps
README.md
# 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`. 

TDQS

B3.2/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have distinct purposes, but there is some overlap between 'restful', 'apex_execute', and 'tooling_execute' as they all involve making API calls to Salesforce, which could cause confusion. The CRUD operations and query tools are clearly differentiated.

Naming Consistency4/5

The naming is mostly consistent with a verb_noun pattern, but there are minor deviations like 'restful' (adjective instead of verb) and 'tooling_execute' (noun_verb instead of verb_noun). Overall, the pattern is readable and predictable.

Tool Count5/5

With 10 tools, the count is well-scoped for a Salesforce connector, covering core operations like CRUD, queries, and API interactions. Each tool serves a specific function without being overwhelming.

Completeness5/5

The tool set provides comprehensive coverage for Salesforce operations, including CRUD, metadata retrieval (get_object_fields), querying (SOQL/SOSL), and various API calls (REST, Apex, Tooling). There are no obvious gaps for typical agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues