Salesforce MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SF_USERNAME | No | Your Salesforce username | |
| SF_ORG_ALIAS | No | Alias for your Salesforce org | |
| SFMCP_HTTP_HOST | No | HTTP server host | 127.0.0.1 |
| SFMCP_HTTP_PORT | No | HTTP server port | 3333 |
| SF_ACCESS_TOKEN | No | Salesforce access token (automatically managed) | |
| SF_INSTANCE_URL | No | Your Salesforce instance URL |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| salesforce_queryC | Run a SOQL query and return JSON rows |
| salesforce_describeC | Describe an SObject and return field information |
| salesforce_list_objectsB | Get list of all Salesforce object names (SObjects) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: describe provides metadata for a specific object, list_objects enumerates all available objects, and query executes data retrieval. An agent can easily differentiate between these three functions.
All tools follow a consistent snake_case pattern with a 'salesforce_' prefix and clear verb_noun structure (describe, list_objects, query). This uniformity makes the tool set predictable and easy to understand.
With only 3 tools, the server feels thin for a Salesforce integration, lacking essential CRUD operations like create, update, or delete. While the tools cover metadata and querying, the absence of data manipulation limits its utility for typical agent workflows.
The tool surface is severely incomplete for a Salesforce domain, missing core operations such as inserting, updating, or deleting records. Agents will hit dead ends when trying to perform basic data modifications, making this server inadequate for comprehensive Salesforce interactions.