Salesforce MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SF_PASSWORD | No | Salesforce password for username/password authentication | |
| SF_USERNAME | No | Salesforce username for username/password authentication | |
| SF_CLIENT_ID | No | OAuth2 client ID from Connected App | |
| SF_LOGIN_URL | No | Salesforce login URL (e.g. https://login.salesforce.com or https://test.salesforce.com) | https://login.salesforce.com |
| SF_INSTANCE_URL | No | Salesforce instance URL (e.g. https://yourorg.my.salesforce.com) | |
| SF_CLIENT_SECRET | No | OAuth2 client secret from Connected App | |
| SF_REFRESH_TOKEN | No | OAuth2 refresh token | |
| SF_SECURITY_TOKEN | No | Salesforce security token (if required, otherwise empty) |
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 |
|---|---|
| test-connectionA | Test Salesforce connection and return organization info |
| execute-soqlB | Execute SOQL query with auto-bulk switching for large result sets |
| execute-soslB | Execute SOSL search with multi-object support |
| describe-sobjectA | Describe SObject metadata with 1-hour caching |
| execute-apexB | Execute anonymous Apex code with debug log capture |
| run-apex-testsC | Run Apex tests with coverage and detailed results |
| get-apex-logsB | Get debug logs with filtering and parsing options |
| create-recordB | Create single or multiple records with auto-bulk switching |
| get-recordB | Retrieve a record by ID with optional field selection |
| update-recordB | Update single or multiple records with auto-bulk switching |
| delete-recordA | Delete records by ID(s) with auto-bulk switching |
| upsert-recordB | Upsert records using external ID with auto-bulk switching |
| deploy-metadataC | Deploy metadata components to Salesforce org |
| retrieve-metadataB | Retrieve metadata components from Salesforce org |
| list-metadata-typesB | List available metadata types in the org for discovery |
| deploy-bundleC | Deploy a metadata bundle (e.g., LWC) from a directory path |
| check-deploy-statusA | Check the status of a deployment |
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 17 tools
Each tool targets a distinct Salesforce operation (record CRUD, queries, metadata, Apex, deployment, connection). Descriptions clearly differentiate between similar tools like deploy-bundle vs deploy-metadata.
All tool names follow a consistent verb-noun pattern with hyphens (e.g., create-record, execute-soql, deploy-metadata). No mixing of conventions.
17 tools cover the core Salesforce development workflow without being excessive. Each tool addresses a specific need and the count is well-proportioned for the domain.
The tool set covers record CRUD, SOQL/SOSL queries, Apex execution and testing, metadata operations, deployment, and connection verification. No obvious gaps for standard Salesforce development tasks.