Skip to main content
Glama
retain-so

Retain MCP Server

Official
by retain-so
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Retain MCP Server

No user-submitted related servers found.

    Related Servers

    • @retainq/mcp

      me-saurabh
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with RetainQ workspaces, including querying retention metrics, managing flows, analyzing churn data, and handling customers, offers, opportunities, and feedback.
      6 npm
      MIT
    • Custify MCP Server by CustifyOfficial

      Custify MCP Serverofficial

      CustifyOfficial
      A
      license
      A
      quality
      F
      maintenance
      Connects AI assistants to Custify customer success data for querying account metrics, health scores, and usage trends. It also supports taking actions such as creating notes, managing tasks, and triggering playbooks.
      15
      21 npm
      3
      MIT

    • Customer Health MCP

      tylerbrabo98
      A
      license
      A
      quality
      C
      maintenance
      Enables an AI assistant to answer customer-success questions by synthesizing simulated billing, support ticket, and product usage data into composite churn-risk scores, bands, and plain-language explanations for fictional accounts. It exposes raw-data tools, a synthesis tool, and a methodology resource so users can list at-risk accounts or get a per-account health summary.
      4
      MIT
    • Summit53 MCP Server by Summit53

      Summit53 MCP Serverofficial

      Summit53
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides 48 revenue intelligence tools that let AI assistants search deals, forecast revenue, analyze pipeline risk, manage outreach, and track value delivery via natural language.
      40 npm
      -
    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/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of churn management: customer lists by risk, individual customer profiles, MRR risk summary, active alerts, churn metrics, and alert actions (note, mark contacted, archive). No two tools have overlapping purposes, and descriptions clearly differentiate them.

    Naming Consistency5/5

    All read operations follow a consistent 'get_' prefix, while write operations use descriptive verb+nouns (add_customer_note, mark_alert_contacted, archive_alert). The naming is uniformly snake_case and predictable, making it easy for agents to infer tool behavior from names.

    Tool Count5/5

    With 8 tools, the set is well-scoped for a churn management server. It covers essential read operations (customer lists, details, metrics, alerts) and write operations (note, contacted, archive) without being bloated or insufficient. The count is appropriate for the domain.

    Completeness4/5

    The tool set covers the core workflow of identifying at-risk customers, monitoring alerts, and managing outreach states. Minor gaps exist, such as the inability to create or resolve alerts programmatically, but the available tools provide sufficient functionality for typical monitoring and action tasks.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources