salesforce-mcp-jsforce
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SF_SCOPE | No | OAuth scopes | api refresh_token |
| SF_READONLY | No | Set to '1' to strip write tools | off |
| SF_CLIENT_ID | No | ECA consumer key for login command | |
| SF_LOGIN_URL | No | OAuth host (sandbox: test.salesforce.com) | https://login.salesforce.com |
| SF_API_VERSION | No | REST API version | 62.0 |
| SF_ACCESS_TOKEN | No | Salesforce access token for stdio mode (optional if token file exists) | |
| SF_INSTANCE_URL | No | Salesforce instance URL for stdio mode (optional if token file exists) | |
| SF_CLIENT_SECRET | No | Client secret for confidential apps |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| salesforce_identityA | Return the identity (user, org, instance) of the supplied token. Use this to confirm the connection is authenticated. |
| salesforce_queryC | Run a SOQL query and return matching records. |
| salesforce_searchB | Run a SOSL full-text search across objects. |
| salesforce_list_objectsA | List all sObjects available in the org with their key metadata. |
| salesforce_describe_objectA | Describe an sObject: its fields, types, picklist values, and references (trimmed payload). |
| salesforce_get_recordB | Retrieve a single record by Id, optionally limited to specific fields. |
| salesforce_create_recordC | Create a new record on the given object. |
| salesforce_update_recordB | Update fields on an existing record. |
| salesforce_delete_recordB | Delete a record by Id. |
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 9 tools
Each tool targets a clearly distinct Salesforce operation: authentication, SOQL query, SOSL search, object metadata listing, single-object description, and record CRUD. There is minimal risk of an agent selecting the wrong tool because the boundaries between query/search, list/describe, and get/query are well-defined.
All tools share the salesforce_ prefix and use snake_case, which creates a strong sense of uniformity. However, salesforce_identity, salesforce_query, and salesforce_search are bare verbs/nouns while the rest use a verb_noun pattern like salesforce_get_record, so there is a minor stylistic deviation.
Nine tools is a well-scoped set for a Salesforce MCP server. Each tool covers a distinct core capability without redundancy, and the count is within the ideal range for an agent to discover and use the full surface comfortably.
The server provides a complete lifecycle for records: get, create, update, and delete, plus query, search, and object metadata inspection. This covers the primary workflows an agent would need when interacting with Salesforce, with no obvious dead ends or missing essential operations.