Connect Churnkey to Claude.
Connecting Churnkey to Claude through Menza lets you put questions to your cancellation sessions, retention metrics, accepted save offers, survey feedback directly in Claude. Menza reads it live through the official Churnkey API, so Claude answers from current numbers, not a stale copy. Ask about performance or have it take an approved action — no exports, no dashboards.
- Reads crm & sales data
- Takes approved actions in Churnkey
- Connects via the official API
Paste your Churnkey API key to connect — it's encrypted and never shown to the AI. or book a demo
How to connect Churnkey to Claude.
Three steps, no pipeline to build and no data to export.
-
In Claude, open Settings → Connectors and add Menza as an MCP server.
-
Authorise the Churnkey connection so Menza can read your Churnkey data on your behalf.
Paste your Churnkey API key to connect — it's encrypted and never shown to the AI.
-
Ask Claude to work with your Churnkey data — it queries Menza live and answers in the chat.
Ready in minutes — connect Churnkey now.
Menza working with Churnkey.
Menza doesn't just answer questions about Churnkey — it proposes the fix and, once you approve, does the work. You stay in control; nothing changes until you say go.
Menzajust nowSave rate in cancellation sessions fell to 21% this week — your 90-day average is 34%. I'll switch the default save offer back to the pause option that was converting at 32% before last week's change, pending your approval.
Menza6m agoPrice is now the stated reason in 44% of cancellation-survey feedback, up from 27% last quarter. I'll add the three-month 20% discount offer to sessions where price is the given reason.
Put Menza between Claude and Churnkey.
Is my Churnkey data secure?
Your credentials are encrypted at rest and never exposed to the AI. Menza reads your data through the provider's official API using the access you grant, and you stay in control of what it can do — read-only by default, with any actions gated behind your approval.
Read our privacy policy- Encrypted in transit and at rest
- Scoped access — you choose what Menza can see
- Read-only by default; any action needs your approval
- Credentials are encrypted and never shown to the AI
- Revoke access at any time
Churnkey + Claude questions, answered.
How do I connect Churnkey to Claude?
Add Menza as an MCP server in Claude, authorise the Churnkey connection once, then ask Claude to work with your Churnkey data. Menza handles the Churnkey API calls for you — there's nothing to export and no pipeline to maintain.
What can Claude do with my Churnkey data through Menza?
Beyond answering questions, Menza can take approved actions in Churnkey on your behalf — for example adjusting or pausing what you ask it to — and every change waits for your approval first, so nothing happens without your say-so.
Is my Churnkey data safe?
Yes. Your Churnkey credentials are encrypted at rest and never shown to the AI. Menza only accesses what you grant it and is read-only by default, with any actions gated behind your approval.