Skip to main content
Glama
RahulModugula

CMR Client Health

Related Servers

Alternatives to CMR Client Health

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Exposes read-only account-health tools for scores, trends, claims checks, risks, pipeline, and next actions, with audience-scoped output for internal or customer views.
      6
      MIT
    • 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
    • F
      license
      Not graded
      quality
      C
      maintenance
      Exposes simulated Salesforce CRM data as MCP tools for Claude Desktop, enabling customer success managers to prioritize at-risk accounts, review opportunities, cases, and Gong notes via natural language.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language Q&A over customer support ticket data. Provides tools for schema inspection, SQL-based ticket counts and grouping, and full-text search for customer wording without requiring API keys.
      -
    • F
      license
      B
      quality
      B
      maintenance
      Exposes client health data through a consolidated tool surface covering sleep, exercise, nutrition, cardio, fitness, cognitive, lifestyle, trends, notes, and chat history. Enables LLMs to retrieve time-series vitals, periodic assessments, unstructured text, and rolled-up summaries via standardized envelopes.
      11
      -

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct aspect: overall health snapshot, listing launcher clients, and lowest performing courses. No overlap in purpose.

    Naming Consistency5/5

    All tools follow a consistent 'get_' prefix followed by descriptive noun phrases, e.g., get_client_health, get_launcher_clients.

    Tool Count4/5

    3 tools is on the low end but well-scoped for a focused health monitoring server. No superfluous tools.

    Completeness4/5

    Covers the key health monitoring needs: overall snapshot, identification of high-risk launcher clients, and renewal risk via course performance. Minor gaps like historical trends or per-user data are acceptable.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues