MCP server for AI-powered churn analysis. Analyze customer cancellation feedback to identify churn patterns, severity ratings, and actionable recommendations.

Tools

analyze_churn

Analyze cancellation feedback to identify why customers are leaving.

Input:

feedback (string, required) — cancellation responses, one per line
focus (string, optional) — narrow analysis to a specific area (e.g., "pricing")

Output: Structured JSON with executive summary, priority action, and categorized insights (reason, count, percentage, severity, confidence, examples, recommendation).

analyze_stripe_churn

Pull canceled subscriptions directly from Stripe and analyze them — no middleware, no DB hookup. Each cancellation is enriched with plan, MRR, sub age, and voluntary vs. involuntary context before being fed to Claude.

Input:

lookback_days (number, optional) — how many days back to analyze. Defaults to 90. Min 7, max 365.
focus (string, optional) — narrow analysis to a specific area (e.g., "pricing")

Requires: STRIPE_SECRET_KEY env var. Use a restricted (read-only) key, not your live secret key. Create one at dashboard.stripe.com/apikeys/create with these permissions:

Subscriptions: Read
Customers: Read
Prices: Read

Output: Same shape as analyze_churn, plus a stripeContext block with totalCanceled, activeSubs, voluntaryCount, involuntaryCount, totalMrrLost, truncated, lowSample, nonUsdSkipped, and noFeedbackRate. When there's not enough data, the Churn Health Score is null rather than fabricated.

get_example_analysis

See a pre-computed example analysis. No API key required.

Input:

scenario (string, optional) — "b2b-saas" (default), "consumer-app", or "pricing"

Installation

Claude Desktop / Claude Code

Add to your MCP config (claude_desktop_config.json or .claude.json):

{
  "mcpServers": {
    "retentioncheck": {
      "command": "npx",
      "args": ["-y", "@retentioncheck/mcp-server"],
      "env": {
        "ANTHROPIC_API_KEY": "your-anthropic-key",
        "STRIPE_SECRET_KEY": "rk_live_..."
      }
    }
  }
}

STRIPE_SECRET_KEY is only required for the analyze_stripe_churn tool. Omit it if you only need text-based feedback analysis.

Cursor

Add to Cursor MCP settings with the same configuration.

Requirements

Node.js 20+
Anthropic API key (for analyze_churn and analyze_stripe_churn)
Stripe restricted key (optional, for analyze_stripe_churn)

Example Usage

Ask your AI assistant:

"Analyze my cancellation feedback" (then paste your data)
"Show me an example churn analysis"
"Why are my customers churning?" (then provide feedback)

Full App

For history, trend tracking, PDF exports, team sharing, and more: retentioncheck.com

Anonymous Telemetry

Starting in 0.2.0, this package sends anonymous usage events to help us understand which tools are used and how. We track:

A randomly generated install ID (UUID, persisted to ~/.retentioncheck-mcp/install-id.json)
Which tool was called (analyze_churn or get_example_analysis)
Whether the call succeeded or failed (and a generic error category if it failed)
Item count for analyze_churn (how many feedback rows were analyzed)
MCP server version, Node version, platform/arch

We do NOT track:

The feedback text itself
Your Anthropic API key or any credentials
Any PII, IP address, hostname, or user identity

To opt out, set RETENTIONCHECK_TELEMETRY=0 in your MCP server's env config:

{
  "mcpServers": {
    "retentioncheck": {
      "command": "npx",
      "args": ["-y", "@retentioncheck/mcp-server"],
      "env": {
        "ANTHROPIC_API_KEY": "your-api-key-here",
        "RETENTIONCHECK_TELEMETRY": "0"
      }
    }
  }
}