Skip to main content
Glama
adamcmyhre

Salesforce MCP Pro

by adamcmyhre
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Salesforce MCP Pro

No user-submitted related servers found.

    Related Servers

    • 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.
      31 npm
      MIT

    • MCP Salesforce Connector

      smn2gnt
      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
      178
      MIT

    • 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.
      31 npm
      MIT

    • ForceKit MCP Server

      rvaghela20
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes Salesforce development tools (scan, lint, test, deploy, verify) to AI assistants via the Model Context Protocol, enabling programmatic interaction with Salesforce projects.
      0
      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
    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

    C2.7/5.0

    Scored across 72 tools

    Disambiguation4/5

    Most tools have clear, distinct resource-action pairs, but some overlap exists: sf_execute_apex_cursor_query and sf_build_apex_cursor_query both handle Apex cursor logic, and ui_action is somewhat vague. Despite the large count, descriptions generally disambiguate well.

    Naming Consistency4/5

    The sf_ prefix with verb_noun pattern is consistent (sf_list_orgs, sf_create_records), and ui_/git_ prefixes also follow a similar pattern. Minor inconsistency like sf_agent_preview_sessions (noun instead of verb) and sf_tooling_list_objects vs sf_list_metadata slightly deviate but overall naming is predictable.

    Tool Count2/5

    72 tools is excessive, far beyond the typical well-scoped range. While the server aims to be comprehensive for Salesforce, the sheer number creates cognitive overload and makes tool selection harder, even if each tool individually serves a purpose.

    Completeness4/5

    The tool surface is extensive, covering queries, CRUD, metadata deploy/retrieve, Apex execution, agents, tests, permission management, UI automation, and git workflows. Minor gaps exist (e.g., no list permission sets tool) but most core Salesforce development workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources