Salesforce MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SALESFORCE_TOKEN | No | Your Salesforce security token | |
| SALESFORCE_PASSWORD | No | Your Salesforce password | |
| SALESFORCE_USERNAME | No | Your Salesforce username/email | |
| SALESFORCE_CONSUMER_KEY | No | Your Connected App's consumer key | |
| SALESFORCE_INSTANCE_URL | No | Your Salesforce instance URL | https://login.salesforce.com |
| SALESFORCE_CONSUMER_SECRET | No | Your Connected App's consumer secret |
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_search_objectsA | Search for Salesforce standard and custom objects by name pattern. Examples: 'Account' will find Account, AccountHistory; 'Order' will find WorkOrder, ServiceOrder__c etc. |
| salesforce_describe_objectA | Get detailed schema metadata including all fields, relationships, and field properties of any Salesforce object. Examples: 'Account' shows all Account fields including custom fields; 'Case' shows all Case fields including relationships to Account, Contact etc. |
| salesforce_query_recordsA | Query records from any Salesforce object using SOQL, including relationship queries. Examples:
Note: When using relationship fields:
|
| salesforce_dml_recordsA | Perform data manipulation operations on Salesforce records:
|
| salesforce_manage_objectA | Create new custom objects or modify existing ones in Salesforce:
|
| salesforce_manage_fieldA | Create new custom fields or modify existing fields on any Salesforce object:
|
| salesforce_search_allA | Search across multiple Salesforce objects using SOSL (Salesforce Object Search Language). Examples:
Notes:
|
| salesforce_upload_report_xmlA | Upload XML to generate or update reports in Salesforce. Examples:
Note: XML must follow Salesforce report metadata format. For custom report types, ensure the report type exists in your org before uploading. |
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 8 tools
Each tool has a clearly distinct purpose with no overlap: describe_object for metadata, dml_records for data manipulation, manage_field/object for schema changes, query_records for SOQL queries, search_all for SOSL searches, search_objects for object discovery, and upload_report_xml for report management. The descriptions reinforce these boundaries, making tool selection unambiguous.
All tools follow a consistent snake_case pattern with a 'salesforce_' prefix and descriptive verb_noun combinations (e.g., salesforce_describe_object, salesforce_query_records). This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming style.
With 8 tools, the server is well-scoped for Salesforce operations, covering key areas like data access, metadata management, and reporting. Each tool serves a specific, non-redundant function, making the count appropriate for the domain without being overwhelming or insufficient.
The tool set provides comprehensive coverage for core Salesforce workflows, including CRUD operations, schema management, querying, and reporting. A minor gap exists in lacking a dedicated tool for handling Salesforce-specific features like Apex code or flows, but agents can work around this using existing tools for most common tasks.