MCP_Salesforce
Related Servers
Alternatives to MCP_Salesforce
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables Claude to query, create, update, and delete Salesforce records directly using SOQL and SOSL, with tools for metadata exploration and bulk operations.-
- AlicenseNot gradedqualityDmaintenanceIntegrates Claude with Salesforce to enable natural language querying, modification, and management of Salesforce records and metadata. It supports comprehensive operations including object/field management, SOSL searches, and Apex code execution.1,360 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude to interact with Salesforce for querying, modifying, and managing objects and records, with automatic integration setup for external services like WhatsApp, Slack, email, and webhooks.-
- AlicenseAqualityDmaintenanceIntegrates Claude with Salesforce for natural language interactions with Salesforce data and metadata, enabling querying, modifying, and managing objects and records.205 npmMIT
- FlicenseAqualityBmaintenanceConnects Salesforce CRM with Claude, enabling CRUD operations, SOQL/SOSL queries, metadata extraction, and sandbox management through natural language.14-
- AlicenseNot gradedqualityCmaintenanceEnables Claude to query live Salesforce org data—accounts, pipeline, cases, campaigns, and journeys—across Sales, Service, and Marketing Cloud, with local or cloud deployment.MIT
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.