MCP Salesforce Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| salesforce_setupC | Configure Salesforce credentials (Client ID, Client Secret, Instance URL) |
| salesforce_learnA | Analyzes the complete Salesforce installation and creates local documentation of all objects, fields, and customizations. This should be run once after initial setup to enable intelligent assistance. |
| salesforce_installation_infoA | Returns comprehensive information about the learned Salesforce installation, including all object details, field specifications, relationships, permissions, and customizations from the learned installation data. |
| salesforce_learn_contextA | Learn and store personal/business context about the user and their Salesforce data model relationships. This helps provide better context-aware assistance across sessions. PROACTIVELY CAPTURE AHA MOMENTS: Whenever you discover something important about the user's workflow, business processes, preferences, challenges, or breakthrough insights during conversations, automatically use store_learning to preserve this knowledge. Look for moments when the user reveals key information, expresses frustration, shares successful strategies, or has realizations - these are valuable learnings that should be stored immediately. |
| salesforce_queryB | Execute SOQL queries against any Salesforce object. Supports SELECT, WHERE, ORDER BY, LIMIT, and other SOQL features. |
| salesforce_createC | Create a new record in any Salesforce object. Automatically handles required fields validation. |
| salesforce_updateC | Update an existing record in any Salesforce object. Requires the record ID and field values to update. |
| salesforce_deleteA | Delete a record from any Salesforce object. This action is permanent and cannot be undone. |
| salesforce_describeA | Get detailed schema information for any Salesforce object, including all fields, data types, and permissions. |
| salesforce_authA | Authenticate with Salesforce. Automatically detects if authentication is needed and handles OAuth flow. Call this tool if any Salesforce operations fail due to authentication issues. |
| salesforce_backupA | Start comprehensive backups of Salesforce data including all file attachments. Runs asynchronously in background - returns immediately with job ID. Check progress with salesforce_backup_status. |
| salesforce_backup_listB | List all available Salesforce backups with their details including timestamp, duration, file counts, and sizes |
| salesforce_backup_statusA | Check the status of Salesforce backup jobs. Monitor running, completed, or failed backup operations. Use without parameters to see all jobs, or specify a job_id to get detailed status of a specific backup job. |
| salesforce_time_machine_queryB | Query historical Salesforce data from backups using Time Machine functionality. Supports point-in-time queries, comparisons, and record history tracking. |
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 14 tools
Most tools have distinct purposes, but there is some overlap between salesforce_describe and salesforce_installation_info, both providing schema details, which could cause confusion. Additionally, salesforce_learn and salesforce_learn_context both involve learning aspects, though their focuses differ slightly (installation vs. personal context).
All tool names follow a consistent snake_case pattern with a 'salesforce_' prefix, and they use clear verbs (e.g., create, delete, query) paired with nouns or actions. This predictability makes the set easy to navigate and understand.
With 14 tools, the server is well-scoped for managing Salesforce operations, covering authentication, CRUD, querying, backups, and setup. Each tool serves a specific function without unnecessary bloat, fitting the domain's complexity appropriately.
The tool set provides comprehensive coverage for Salesforce interactions, including full CRUD operations (create, query, update, delete), schema exploration (describe, installation_info), backup management, authentication, setup, and advanced features like time machine queries. No significant gaps are apparent for the intended domain.