Connects Claude directly to your churn data through Stripe, Postgres, or MySQL using read-only credentials that stay in your local MCP config. Exposes four tools: analyze_churn for pasted feedback, analyze_stripe_churn to pull canceled subscriptions with MRR and cancelation context, analyze_sql_churn that generates safe SELECT queries from your schema description, and get_example_analysis for output shape preview. Returns structured insights with severity scores, confidence ratings, and specific recommendations ranked by impact. Built for agents to reason about retention without leaving your editor. The SQL tool hard-caps at 500 rows, applies 15-second timeouts, and validates table names against an allowlist before execution. If you run a SaaS and want churn analysis in your coding workflow without CSV exports or dashboard context switching, this slots in fast.
ANTHROPIC_API_KEYsecretAnthropic API key for running churn analysis (required for analyze_churn, analyze_stripe_churn, and analyze_sql_churn; get_example_analysis works without it).
STRIPE_SECRET_KEYsecretStripe API key for analyze_stripe_churn. Use a RESTRICTED (read-only) key with these permissions: Subscriptions Read, Customers Read, Prices Read. Create one at https://dashboard.stripe.com/apikeys/create. Optional — only required for the analyze_stripe_churn tool.
POSTGRES_URLsecretPostgres connection string for analyze_sql_churn when dialect='postgres'. Format: postgres://user:pass@host:5432/db?sslmode=require. Use a READ-ONLY user — see retentioncheck.com/integrations for the exact GRANT SQL. Optional — only required for the analyze_sql_churn tool with po
MYSQL_URLsecretMySQL connection string for analyze_sql_churn when dialect='mysql'. Format: mysql://user:pass@host:3306/db?ssl=true. Use a READ-ONLY user — see retentioncheck.com/integrations for the exact GRANT SQL. Optional — only required for the analyze_sql_churn tool with mysql dialect.
RETENTIONCHECK_TELEMETRYSet to 0 to opt out of anonymous usage telemetry. Telemetry tracks tool invocations and aggregate counts — never the feedback text, financial values, or any PII.
hovecapital/read-only-local-postgres-mcp-server
cocaxcode/database-mcp
io.github.infoinlet-marketplace/mcp-mysql
io.github.cybeleri/database-admin
io.github.yash-0620/postgres-mcp-secured