Salesforce MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SALESFORCE_PASSWORD | Yes | Your Salesforce password | |
| SALESFORCE_USERNAME | Yes | Your Salesforce username | |
| SALESFORCE_SECURITY_TOKEN | Yes | Your 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 | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_objectsA | List all available Salesforce objects. Returns: List of dictionaries containing object metadata including name, label, whether it's custom, and other attributes. |
| describe_objectA | Get all fields for a specific Salesforce object. Args: object_name: The API name of the Salesforce object (e.g., 'Account', 'Contact') Returns: Dictionary containing object name and list of field definitions. |
| get_soql_helpA | Get comprehensive help documentation for SOQL (Salesforce Object Query Language). Returns: Dictionary containing SOQL syntax guide, examples, best practices, and common patterns. |
| execute_soql_queryA | Execute a SOQL query against Salesforce. Args: query: The SOQL query string (e.g., 'SELECT Id, Name FROM Account LIMIT 10') Returns: Dictionary containing query, rows, row_count, and columns. IMPORTANT: Before constructing SOQL queries, use the get_soql_help() tool to understand: - Basic SOQL syntax and structure - How to write WHERE clauses and filters - Relationship queries (child-to-parent and parent-to-child) - Aggregate functions and GROUP BY - Common patterns and best practices Important SOQL Rules: 1. CANNOT use SELECT * - You MUST specify column names explicitly 2. Aggregate queries (using COUNT, SUM, AVG, etc.) CANNOT use LIMIT |
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 4 tools
Each tool targets a distinct responsibility: listing objects, describing an object, providing SOQL help, and executing a query. There is no overlap in purpose or confusion about which tool to use.
All tool names follow a consistent verb_noun pattern in snake_case (list_objects, describe_object, get_soql_help, execute_soql_query). This is uniform and predictable.
Four tools is well within the ideal range and each tool serves a clear, non-redundant function. The count feels appropriate for the server's focused scope of metadata access and SOQL execution.
The server lacks any record-level CRUD operations (create, update, delete) or a direct 'get record' tool, which are expected from a Salesforce MCP server. While it covers schema discovery and querying, significant functional gaps remain for real-world automation.