Skip to main content
Glama
matheswarwan

mcp-interaction-studio

by matheswarwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-interaction-studio

No user-submitted related servers found.

    Related Servers

    • Salesforce MCP Server

      tsmztech
      A
      license
      A
      quality
      A
      maintenance
      An MCP server implementation that integrates Claude with Salesforce, enabling natural language interactions with Salesforce data and metadata for querying, modifying, and managing objects and records.
      15
      1,426 npm
      167
      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
      -

    • 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.
      29 npm
      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

    B3.4/5.0

    Scored across 22 tools

    Disambiguation3/5

    Tools are mostly distinct but several overlap: list_segments vs list_all_segments, get_segment vs get_segment_details, and audit_dataset vs audit_mcp_dataset could confuse an agent. Descriptions help differentiate but ambiguity remains.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with lowercase and underscores (e.g., list_recipes, set_campaign_state). The verbs vary appropriately but the pattern is uniform across all 22 tools.

    Tool Count4/5

    22 tools is on the higher side of reasonable for a complex domain like Interaction Studio, covering datasets, campaigns, segments, recipes, and audits. It is slightly above the typical well-scoped range but not excessive.

    Completeness2/5

    The tool set heavily favors read operations and state toggles but lacks create, update, or delete tools for campaigns, segments, recipes, or surveys. This is a significant gap for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources