Skip to main content
Glama
tsmztech

Salesforce MCP Server

by tsmztech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Salesforce MCP Server

No user-submitted related servers found.

    Related Servers

    • Salesforce MCP Server

      savidev1987
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server implementation that integrates Claude/VS Code with Salesforce, enabling natural language interactions with your Salesforce data and metadata.
      MIT

    • salesforce-mcp

      ryu-727
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides comprehensive access to Salesforce Tooling API for metadata management, SOQL queries, code analysis, and debugging through Claude and other AI assistants.
      25 npm
      5
      MIT

    • salesforce-remote-mcp

      tsmztech
      A
      license
      Not graded
      quality
      C
      maintenance
      A remote MCP server for Salesforce deployed on Cloudflare Workers, enabling Claude to query and manage Salesforce data through SOQL, SOSL, DML, and Apex with per-user OAuth.
      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
      7
      -
    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

    A4.2/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource/action pair. Query vs. aggregate query are explicitly disambiguated via cross-references; search objects (metadata) vs. search all (records) are differentiated; Apex class and trigger tools are separate. No genuine overlap.

    Naming Consistency5/5

    All tools consistently use the 'salesforce_' prefix followed by snake_case names with verb-like prefixes (describe, query, search, manage, read, write, execute). Minor deviations like 'aggregate_query' and 'execute_anonymous' still fit the overall predictable pattern.

    Tool Count5/5

    15 tools is at the upper end of the ideal range, but each tool earns its place by covering distinct Salesforce workflows: data querying, DML, metadata management, Apex code, and debug logs. No redundancy or bloat.

    Completeness4/5

    The tool set provides solid lifecycle coverage: record CRUD via dml_records, query and aggregate query, SOSL search, object/field metadata management, Apex class/trigger read/write, and anonymous execution. The main gap is lack of explicit delete operations for metadata (objects, fields, Apex classes/triggers), but execute_anonymous can act as a workaround in some cases.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources