Skip to main content
Glama
ampcome-mcps

MCP Salesforce Connector

by ampcome-mcps

Related Servers

Alternatives to MCP Salesforce Connector

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      A Model Context Protocol server that enables LLMs to interact with Salesforce data through SOQL queries, SOSL searches, and various API operations including record management.
      14
      124 PyPI
      177
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A TypeScript implementation of a Model Context Protocol server that enables LLMs to interact with Salesforce data through SOQL queries, SOSL searches, and CRUD operations.
      2
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      A customizable MCP server for integrating Salesforce APIs with GenAI applications, supporting SOQL queries, record CRUD, metadata access, and more.
      13
      7
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that connects AI assistants to Salesforce orgs, enabling querying, searching, creating, updating, and managing Salesforce data through natural language via any MCP-compatible client.
      60 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to securely query, search, and modify Salesforce data through standard Salesforce APIs, including record CRUD, SOQL/SOSL search, Bulk API 2.0 operations, composite calls, object discovery, and custom Apex REST endpoints.
      15
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to securely read, manage, and operate Salesforce org resources through Model Context Protocol tools.
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap between 'restful', 'apex_execute', and 'tooling_execute' as they all involve making API calls to Salesforce, which could cause confusion. The CRUD operations and query tools are clearly differentiated.

    Naming Consistency4/5

    The naming is mostly consistent with a verb_noun pattern, but there are minor deviations like 'restful' (adjective instead of verb) and 'tooling_execute' (noun_verb instead of verb_noun). Overall, the pattern is readable and predictable.

    Tool Count5/5

    With 10 tools, the count is well-scoped for a Salesforce connector, covering core operations like CRUD, queries, and API interactions. Each tool serves a specific function without being overwhelming.

    Completeness5/5

    The tool set provides comprehensive coverage for Salesforce operations, including CRUD, metadata retrieval (get_object_fields), querying (SOQL/SOSL), and various API calls (REST, Apex, Tooling). There are no obvious gaps for typical agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues