Skip to main content
Glama
tylerbrabo98

Customer Health MCP

by tylerbrabo98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Customer Health MCP

No user-submitted related servers found.

    Related Servers

    • CSM Intelligence MCP Server

      maheshsane
      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.
      -
    • Retain MCP Server by retain-so

      Retain MCP Serverofficial

      retain-so
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to query customer churn risk, MRR at risk, and customer health profiles from Retain, and take actions like adding notes and marking alerts contacted.
      8
      24 npm
      1
      MIT

    • infera-mcp-server

      rdndelgado
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query internal business data for insights into customers, revenue, subscriptions, sales, and churn through controlled, read-only MCP tools.
      -

    • finance-mcp-server

      hadiagha0
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to query a synthetic general ledger and trial balance through read-only tools for account lookups, GL drill-down, variance analysis, and naive forecasting, with every answer cited to specific transactions or periods.
      24 npm
      MIT

    • lodestar

      roshanrana
      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
    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 4 tools

    Disambiguation4/5

    list_accounts and list_at_risk_accounts both return account lists and could be momentarily confused, but the descriptions make the filtering intent distinct (plan/payment vs risk band). get_account_details (raw data) vs get_account_risk_summary (synthesized score/drivers) are cleanly separated.

    Naming Consistency5/5

    All four tools follow a consistent snake_case verb_noun pattern using list_/get_ prefixes and predictable noun phrases. No mixing of conventions or stylistic outliers.

    Tool Count4/5

    Four read-only tools is well-scoped for a churn-risk analytics surface, with no redundant entries. It is slightly lean—no mutation or annotation tools—but each tool earns its place.

    Completeness4/5

    The read-only lifecycle is well covered: overview, at-risk ranking, raw detail, and risk synthesis with explicit follow-up pathways. Minor gaps exist (no way to list support tickets globally, no account-level write/annotation), but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources