Churnkey MCP: subscriber retention
Churnkey MCP
The Churnkey MCP server: an agent reads subscription cancel data, edits retention flows and runs A/B tests
- 24 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent changes billing settings and publishes flows customers see at once, so a mistake hits revenue
- The dsr_access tool reads customer data by email, and personal fields open under a separate scope
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/churnkey-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent changes billing settings and publishes flows customers see at once, so a mistake hits revenue
- The dsr_access tool reads customer data by email, and personal fields open under a separate scope
This is third-party code. Review the repository files before installing.
What it does
Churnkey builds the flows a customer meets when canceling a subscription: a reason survey, a discount, a pause, a plan change. The churnkey/sdk repository holds three packages: a React component for the cancel flow, a server package for tokens and @churnkey/mcp. The MCP server reads Churnkey account data: cancel sessions, results by offer type, recovered failed payments and the audit log. It also edits configuration. The agent creates a flow draft, changes steps and offers, adds and reorders survey choices, sets audience segments and starts an A/B test. Publishing a draft needs confirmation and is written to the audit log. Other tools edit the emails and SMS of payment recovery campaigns, hosted page domains and billing settings such as proration, cancellation timing and pause behavior. A customer data lookup by email (GDPR and CCPA access) exists, while erasure is deliberately left out of MCP.
Who it is for. Subscription SaaS product teams that run cancellations and payment recovery in Churnkey and want to work through them with an agent.
Good fit when
- Cancellations grew over a quarter and you want to see which plans and reasons lose customers
- You want to swap a cancel-time discount for a pause and compare the result in an A/B test
- Failed-payment emails are stale and need rewriting step by step
- A new customer segment needs its own cancel flow with its own offers
- Before a release you want the audit log: who changed what in the flow
Not a fit when
- You only need the React cancel component, which installs as @churnkey/react and does not need MCP
- You need to erase customer data: MCP does not offer erasure, it goes through the dashboard or the Data API
- You want to change the live flow without sign-off: publishing and editing live segments change what customers see
- You need figures from the last few minutes: sessions refresh about every three hours
Example request
Show the retention overview for 90 days and tell me which offer type saves the most customers on the annual plan.MCP
- Transport
- stdio, http
- Authentication
- OAuth
Environment variables
CHURNKEY_MODE- live or test: session data mode, live by default
CHURNKEY_CONFIG_DIR- Token directory, ~/.churnkey by default
CHURNKEY_API_URL- API address, https://api.churnkey.co/v1 by default
Limitations
A workspace admin must enable MCP access for your user under Team, or sign-in fails.
Session analytics refresh about every three hours and recovery campaigns about every 20 minutes.
Customer identity fields arrive redacted until you grant their scopes explicitly at sign-in.
Data API keys are deprecated for MCP: they give read-only access, and configuration writes with them are rejected.
How to disable. Remove the server with claude mcp remove churnkey. Revoke the session with npx @churnkey/mcp auth logout, which revokes the token and deletes the token file in ~/.churnkey.
FAQ
How do I connect Churnkey MCP to Claude Code?
First sign in with npx @churnkey/mcp auth login, which opens a browser consent screen. Then run claude mcp add churnkey -- npx -y @churnkey/mcp and restart the Claude Code session. No keys go into the config.
Do I need an API key?
No, sign-in uses OAuth 2.1 as your Churnkey user. Scopes come from your role, and you can narrow them on the consent screen. Old Data API keys still work but only for reading.
Can the agent publish a flow without me?
Technically yes, but publish_blueprint requires a confirmation parameter and the action lands in the audit log under your name. Ask the agent to show the draft before publishing.
How do I tell test data from live data?
Setting CHURNKEY_MODE=test switches session analytics to test mode. Flow and campaign configuration is shared across modes, so edits show up in both.
Do I need the React component to use MCP?
No. The MCP server works with your Churnkey account and does not require @churnkey/react in your app. You need the component only to embed the cancel flow in your own interface.
Discussion
No questions or reviews yet.
Related
MCP serversHosted MCP server for Amazon Ads and Seller Central: the agent reviews ACoS, search terms and stock, edits on confirmation
Open-source CRM for small teams with MCP: contacts, deals and tasks open to Claude and other agents, with reply drafts left to you
amoCRM sales manager MCP server
amoCRM ROP MCP Server
An MCP server with business tools on top of amoCRM for a sales manager: department overview, stale deals, manager comparison
A set of MCP servers for Wildberries, Ozon, Yandex Market, Bitrix24, amoCRM, Avito, Direct, Metrika, Webmaster and DaData, free locally
SendPulse MCP server for WhatsApp and SMS
SendPulse MCP Server
An MCP server for SendPulse WhatsApp bots and SMS: contacts, button messages, flows, triggers and live chat
RetailCRM MCP
retailcrm-mcp
RetailCRM MCP server: orders, customers, products, stock, payments, tasks and store analytics via API v5
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Churnkey MCP: subscriber retention (this card) | yes | OAuth | 24 | |
| MCP Server for Paddle Billing | yes | API key | 50 | works with Paddle billing rather than cancel flows and payment recovery |
| Stripe AI | yes | OAuth | 2,059 | tools for the Stripe payments platform without retention flows |
README in short
The repository README describes three packages: @churnkey/react with a ready-made cancel flow, @churnkey/node for server tokens and @churnkey/mcp. Packages are published to npm with provenance, and the MCP server also goes to the MCP Registry.