Salesforce MCP Server
Related Servers
Alternatives to Salesforce MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Salesforce orgs through natural language commands, supporting org management, SOQL queries, metadata operations, testing, and more.1-
- AlicenseAqualityCmaintenanceEnables interaction with Salesforce orgs to perform operations like querying data with SOQL, managing records, and executing Apex code. It provides configurable access levels and support for both standard and Tooling APIs via natural language interfaces.11MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to interact with Salesforce data by listing objects, describing fields, and executing SOQL queries.4-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Salesforce organizations through project-based CLI integration, allowing execution of Apex, SOQL queries, object descriptions, and org management using local Salesforce DX project configurations.MIT
- AlicenseNot gradedqualityFmaintenanceConnects any MCP-compatible AI assistant directly to a Salesforce org for querying data, exploring schema, running Apex, and managing deployments.7 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables secure interaction with Salesforce orgs through LLMs, providing tools for managing orgs, querying data, deploying metadata, running tests, and performing code analysis with granular access control and encrypted authentication.Apache 2.0
TDQS
Scored across 40 tools
Most tools target distinct Salesforce operations, but several overlap: run_code_analyzer, scanner_run, and scanner_run_dfa all perform code analysis; apex_get_log vs apex_log_list and query_records vs query_records_to_file require reading descriptions to distinguish. These overlaps keep the set from being cleanly disambiguated.
Tools are mostly snake_case, but ordering is inconsistent: verb_noun (create_record, list_metadata) mixes with noun_verb (sobject_list, apex_log_list, package_install, scanner_run, deploy_start). Some generic names like open and logout lack resource context, though the set remains readable.
40 tools is excessive for a single MCP server, even for the broad Salesforce domain. Several niche CLI wrappers could be consolidated, especially the code-analysis trio and the two query_records variants, making the surface feel bloated rather than well-scoped.
Coverage spans core Salesforce domains: org auth/config, record CRUD, SOQL/SOSL, metadata listing, Apex tests/execution, deployment, packages, code analysis, and logging. Minor gaps like metadata retrieve/update/delete and direct record get are workaroundable, so the surface is broadly complete.