MCP_Salesforce
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_CLIENT_ID | Yes | Connected App Consumer Key | |
| SALESFORCE_LOGIN_URL | Yes | Salesforce login URL (usually https://login.salesforce.com) | |
| SALESFORCE_CLIENT_SECRET | Yes | Connected App Consumer Secret | |
| 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_accountsA | Search for Salesforce accounts by name, industry, or other criteria |
| search_contactsB | Search for Salesforce contacts by name, email, or other criteria |
| search_opportunitiesB | Search for Salesforce opportunities by name, stage, or other criteria |
| search_leadsB | Search for Salesforce leads by name, company, or other criteria |
| get_account_detailsA | Get detailed information about a specific Salesforce account |
| get_contact_detailsA | Get detailed information about a specific Salesforce contact |
| get_opportunity_detailsB | Get detailed information about a specific Salesforce opportunity |
| update_accountB | Update a Salesforce account with new information |
| update_contactB | Update a Salesforce contact with new information |
| update_opportunityC | Update a Salesforce opportunity with new information |
| get_recent_activitiesC | Get recent activities (tasks, events, calls) for an account or contact |
| create_taskB | Create a new task in Salesforce |
| create_accountC | Create a new Salesforce account |
| create_contactB | Create a new Salesforce contact |
| create_opportunityB | Create a new Salesforce opportunity |
| search_all_recordsA | Search across all Salesforce records using SOSL (global search) |
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 16 tools
Each tool clearly targets a distinct Salesforce object and action (search, get, update, create). The global search_all_records is distinct from object-specific searches by its SOSL nature. No two tools appear to overlap in purpose.
Tool names follow a consistent verb_noun pattern in snake_case (e.g., search_accounts, create_task). Minor deviations include get_recent_activities lacking the '_details' suffix used by other getters, and search_all_records being a slightly different phrase, but the overall convention is predictable.
Sixteen tools is slightly above the typical 3-15 range but justified for covering multiple CRM objects (Account, Contact, Opportunity, Lead, Task) with search, get, update, and create operations. The count is reasonable and not bloated.
Significant gaps exist: no delete operations for any object, Lead only has search (no get, update, or create), and Task only has create. This leaves agents unable to perform full lifecycle management, which is a notable deficiency for a Salesforce server.