Skip to main content
Glama
smn2gnt

MCP Salesforce Connector

by smn2gnt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MCP Salesforce Connector

No user-submitted related servers found.

    Related Servers

    • salesforce-mcp

      uoparaji
      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

    • Salesforce MCP Server

      steffensbola
      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

    • MCP Salesforce Connector

      ampcome-mcps
      A
      license
      B
      quality
      D
      maintenance
      A server implementation that enables LLMs to interact with Salesforce data through SOQL queries, SOSL searches, and API operations including retrieving, creating, updating, and deleting records.
      10
      1
      MIT

    • Salesforce MCP Server

      uday210
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables interaction with Salesforce through REST API using jsforce, allowing users to execute SOQL queries, retrieve object metadata, and perform CRUD operations on Salesforce records.
      60 npm
      MIT

    • Salesforce MCP Server

      LokiMCPUniverse
      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
      8
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct operation: CRUD, bulk CRUD, queries, metadata, and direct API calls. Overlaps like get_record vs run_soql_query are clarified by different access patterns (ID vs query). Apex and tooling executes are differentiated by API type.

    Naming Consistency4/5

    Most tools follow snake_case verb_noun pattern (e.g., create_record, run_soql_query). Exceptions include 'restful' (single word) and plural in bulk tools (bulk_create_records) vs singular in standard tools (create_record), causing minor inconsistency.

    Tool Count5/5

    14 tools cover a broad Salesforce use case without being excessive. Each tool has a clear purpose, and the count is well-scoped for a comprehensive connector.

    Completeness4/5

    The tool set covers CRUD, bulk operations, queries, searches, object metadata, and direct API calls. Minor gaps include absence of upsert or describe metadata operations, but core workflows are fully supported.

    Maintenance

    ActivityStale
    ResponsivenessResponsive

    Resources