Skip to main content
Glama
advancedcommunities

Salesforce MCP Server

by advancedcommunities
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Salesforce MCP Server

No user-submitted related servers found.

    Related Servers

    • Salesforce CLI MCP Server

      timaw513-emergenit
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Salesforce orgs through natural language commands, supporting org management, SOQL queries, metadata operations, testing, and more.
      1
      MIT

    • Salesforce MCP Server

      mintmcp
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      11
      MIT

    • Salesforce MCP Server

      aiyanbo
      F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Salesforce data by listing objects, describing fields, and executing SOQL queries.
      4
      -

    • Salesforce CLI MCP Server

      perrynet
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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

    • Salesforce DX MCP Server

      kodey-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 47 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions, and descriptions include explicit cross-references (e.g., query_records defers to search_records; sobject_list advises running before queries). However, run_code_analyzer vs scanner_run/scanner_run_dfa overlap in code quality/security scanning, and the metadata listing tools (sobject_list, list_metadata, list_metadata_types) can be confused. These overlaps are mostly mitigated by detailed guidance, so the set is largely distinct.

    Naming Consistency3/5

    Many tools follow a verb_noun pattern (create_record, run_apex_tests, list_metadata), but a substantial minority use noun_verb or noun_noun (sobject_list, apex_get_log, bulk_job_status, scanner_run, package_install, schema_generate_tab). This mix reduces predictability even though the names remain readable. The convention is inconsistent enough to matter.

    Tool Count2/5

    47 tools is far above the typical well-scoped range and includes several fragmented utilities (multiple code analyzers, multiple metadata listers, separate default-org get/set/clear). While Salesforce is a broad domain, the count is heavy and over-fragmented, creating unnecessary selection overhead for agents.

    Completeness4/5

    The surface covers core workflows well: org auth, record CRUD, bulk insert/update/upsert/delete, SOQL/SOSL query, Apex execute/tests/logs, metadata list/deploy, package install/uninstall, permissions, and code analysis. Notable gaps remain, such as metadata retrieve (pull from org) and scratch org create/delete, plus no direct get-record-by-Id (though query covers it). These are workable gaps in an otherwise comprehensive surface.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources