Developer API & MCP — read-only v1

Plug your AI into your churn.

ChurnWin collects cancellation feedback and churn signals from your Stripe customers. The developer API and MCP server let your AI agent read that data and tell you what to build or fix to reduce churn — without writing a single SQL query.

Start free Get your API key

Two ways to connect

Both options use the same API key, scoped to your ChurnWin account.

MCP server

Connect any MCP-compatible AI client (Claude, Cursor, Windsurf…) directly to ChurnWin. Your agent discovers all available tools automatically — no hand-written prompts needed.

MCP setup guide

REST API

Standard JSON over HTTPS. Point any HTTP-capable agent at https://api.churnwin.com/api/v1/agent and start querying. A machine-readable OpenAPI spec is available too.

REST API reference

Recovery workflow

Build a failed-payment recovery snapshot

Start with one bounded, read-only workflow instead of importing every customer field. MCP and REST expose the same ChurnWin evidence, so choose the transport your runtime already supports and keep the period and Stripe-business scope explicit.

1. Scope
Confirm the connected business
Use list_businesses with MCP or GET /businesses with REST. If the key can see multiple Stripe accounts, carry the intended numeric business id into every later call.
2. Measure
Read a 30-day recovery snapshot
Call get_metrics with MCP or GET /metrics?period=30d&business=<id> with REST. Record payment_failures, recovered_count, recovered_mrr, and at_risk_mrr. A returned zero is evidence, not a placeholder to replace with an estimate.
3. Review
Separate evidence from the next action
Add recent events with list_recent_churn or GET /recent-churn, then read the stored recommendation with get_action_plan or GET /action-plan. Label observed values and recommendations separately before a person chooses what to do.

Keep billing changes and customer contact under human review

ChurnWin's v1 API and MCP tools can read recovery signals; they cannot retry a payment, edit a subscription, or contact a customer. Review the business scope, reporting window, and evidence before moving a recommendation into a billing or outreach system.

Preview the recovery audit

What your agent can read

All endpoints are read-only in v1. The API key grants no write permission and can be limited to one connected Stripe business.

Churn metrics & trend

Churn rate, MRR, retention over any period

At-risk customers

AI risk scores and signals for every subscriber

Churn reasons

Aggregated cancellation reason breakdown

Cancellation feedback

Verbatim survey responses from churned users

AI action plan

ChurnWin's prioritised retention recommendations

Recent churn

Latest churned customer list with MRR lost

Customer list

Full customer roster filterable by status

Feedback performance

Survey send/open/response rates over time

Businesses

All Stripe accounts connected to ChurnWin

Who it's for

Indie SaaS founders

Drop your MCP config into Claude and ask it what's driving churn this month — no dashboard diving.

Developer-led teams

Pipe churn data into your own AI workflows, internal tools, or Slack bots via the REST API.

AI-native builders

Build agents that cross-reference churn feedback with your product roadmap and suggest what to ship next.

Agent quickstarts

Platform-specific setup pages for teams searching how to plug churn feedback into their AI agent stack.

Claude Sonnet 4 / Claude Code

Connect Claude to ChurnWin MCP and draft retention work from churn themes.

Hermes Agent

Add ChurnWin as a native MCP server for daily SaaS feedback-to-issues loops.

OpenClaw

Give OpenClaw-style coding agents customer churn context before they write code.

Authentication

Every request requires an Authorization: Bearer cwk_live_… header. Keys are minted — and revoked — from Settings → Agent Access. You need an active ChurnWin plan to create keys.

Read-only scope — API keys cannot modify or delete your data.

Developer references

Set up the connection, adapt a proven agent workflow, and review the data-safety boundaries.

MCP setup guide

Endpoint, config snippet, and the complete read-only tool set

REST API reference

Endpoints, parameters, and JSON examples for custom runtimes

Agent workflow examples

Copyable patterns for turning churn evidence into product work

Agent access security

Read-only scopes, key handling, redaction, and human review