mcp-server-salesforce
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port. Default: 3000 | 3000 |
| LOG_LEVEL | No | Log level. Default: info | info |
| SALESFORCE_PASSWORD | Yes | Salesforce password | |
| SALESFORCE_USERNAME | Yes | Salesforce username | |
| SALESFORCE_CLIENT_ID | Yes | Salesforce Connected App client ID | |
| SALESFORCE_LOGIN_URL | No | Salesforce login URL. Default: https://login.salesforce.com | https://login.salesforce.com |
| SALESFORCE_CLIENT_SECRET | Yes | Salesforce Connected App client secret | |
| SALESFORCE_READ_ONLY_MODE | No | Start in read-only mode. Default: true | true |
| SALESFORCE_SECURITY_TOKEN | Yes | Salesforce security token |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_recordsC | Search for Salesforce records across multiple objects |
| soql_queryB | Execute a SOQL query against Salesforce (read-only) |
| global_searchB | Perform a global search across all Salesforce objects |
| get_recordB | Retrieve a specific Salesforce record by ID |
| get_related_recordsC | Get records related to a specific record |
| get_record_historyB | Get the field history for a record |
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 6 tools
Tools like search_records and global_search have overlapping purposes, both searching across objects. Their descriptions do not clearly differentiate them, causing potential confusion for an agent.
Most tool names follow a verb_noun pattern (e.g., get_record, search_records), but global_search is noun_verb, and soql_query is a slight deviation. Overall, the pattern is mostly consistent.
With 6 tools, the server is well-scoped for read-only Salesforce operations. Each tool serves a clear purpose without redundancy, and the count is appropriate for the domain.
The tool set covers only read operations (queries and retrievals). Missing create, update, delete, and metadata discovery tools create significant gaps for typical Salesforce workflows.