Churnkey MCP. Manage retention actions and billing updates from chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Churnkey. Manage customer retention and billing recovery directly from your AI client. This server lets your agent analyze exit surveys, list specific cancellation sessions, and update billing contacts for multiple customers—all without opening the Churnkey dashboard.
What your AI agents can do
Bulk update billing contacts
Updates the billing recovery contacts for multiple customers simultaneously.
Delete customer gdpr data
Permanently removes all customer data to meet GDPR compliance standards.
Get customer gdpr data
Retrieves all stored customer data, fulfilling a data access request for GDPR compliance.
Retrieve grouped session counts to find patterns in why customers are leaving.
List every cancellation session for a specific customer ID to build a full retention record.
Update recovery contacts for a specific customer or update contacts for many customers at once.
Get all the details for one cancellation flow session.
Access or delete all data associated with a customer ID for GDPR compliance.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
019d756fbulk update billing contacts
Updates the billing recovery contacts for multiple customers simultaneously.
019d756fdelete customer gdpr data
Permanently removes all customer data to meet GDPR compliance standards.
019d756fget customer gdpr data
Retrieves all stored customer data, fulfilling a data access request for GDPR compliance.
019d756fget retention session details
Retrieves full details for a single, specific customer cancellation session.
019d756fget session aggregates
Calculates and returns grouped counts of retention sessions to identify broad trends.
019d756flist customer retention history
Retrieves a chronological list of all cancellation sessions tied to one customer ID.
019d756flist retention sessions
Lists all recent cancellation flow sessions across your entire user base.
019d756fupdate billing contacts
Updates the billing recovery contacts for a single, specific customer.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Churnkey, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Your AI client uses the Churnkey MCP Server to handle retention and billing stuff without you ever touching the Churnkey dashboard. You can run deep analyses and handle customer service tasks right from your chat window. You'll be able to check a customer's cancellation history, analyze trends across your user base, and manage billing contacts for one or many people.
To analyze retention trends, you've got tools like get_session_aggregates to count grouped retention sessions, which shows you what's happening across your whole user base. You can also use list_retention_sessions to pull a list of all recent cancellation flow sessions.
To check a customer's cancellation history, run list_customer_retention_history to get every cancellation session tied to a specific customer ID. You can also pull the full details for one specific cancellation flow session using get_retention_session_details.
For managing billing contacts, you can update recovery contacts for a single customer with update_billing_contacts, or you can update contacts for a bunch of customers all at once using bulk_update_billing_contacts.
For compliance, you can fulfill data requests by retrieving all stored customer data with get_customer_gdpr_data, or you can permanently delete all customer data to meet GDPR standards using delete_customer_gdpr_data.
How Churnkey MCP Works
- 1 Subscribe to the Churnkey server and input your Churnkey Data API Key and App ID.
- 2 Instruct your AI client to perform a task (e.g., 'List all retention sessions for customer X').
- 3 The agent executes the necessary tool call, returning structured data—like retention rates or updated contact statuses—directly to your chat.
The bottom line is that your AI client executes complex Churnkey operations and hands you the results, all from a single chat window.
Who Is Churnkey MCP For?
This is for SaaS founders, Customer Success Managers, Finance teams, and Operations engineers. If your job involves monitoring why people cancel, tracking failed payments, or making sure you comply with data deletion requests, this server cuts out the dashboard clicks. You get the data and the actions in one place.
Reviews a specific customer's entire cancellation history by running the list_customer_retention_history tool, so they know exactly what retention offers the customer was presented with.
Analyzes monthly churn trends by calling get_session_aggregates to identify the top three reasons customers are leaving the product.
Manages failed payment recovery by using bulk_update_billing_contacts to update payment details for dozens of accounts at once.
Handles data privacy requests by executing delete_customer_gdpr_data and confirming the deletion of a customer's records.
What Changes When You Connect
- Check a customer's full cancellation history using
list_customer_retention_history. You don't have to open the dashboard to see every pause, discount, or cancellation reason they were shown. - Run bulk billing updates with
bulk_update_billing_contacts. Instead of updating payment details one by one, your agent handles groups of accounts instantly. - Figure out macro trends with
get_session_aggregates. Running this tool shows you the top reasons for churn across the entire user base, saving hours of manual report building. - Maintain compliance easily. Use
delete_customer_gdpr_dataorget_customer_gdpr_datato manage all customer data requests without leaving your AI chat. - Deep-dive into specific losses. Use
get_retention_session_detailsto pull every piece of data from a single, critical cancellation session for review.
Real-World Use Cases
Auditing a high-value client's churn
A CSM needs to know why 'cust_999' left. They ask their agent to run list_customer_retention_history. The agent returns two sessions: one where the user accepted a '3 month pause' and another where they canceled due to 'Product complexity'. The CSM uses this history to craft a better retention pitch.
Quarterly GDPR cleanup
The compliance officer needs to wipe data for 50 accounts. They prompt the agent to use delete_customer_gdpr_data for a list of IDs. The agent confirms the deletion across all records, ensuring the company meets its legal obligations without manual spreadsheet work.
Mass payment detail cleanup
The finance team identifies 20 accounts with outdated billing information. Instead of opening 20 dashboards, they ask the agent to run bulk_update_billing_contacts with the new payment details, updating all records in one API call.
Understanding macro pricing issues
The founder notices a spike in churn. They ask the agent to run get_session_aggregates. The result shows 'Price' is the top reason for leaving (60% of sessions), immediately guiding product focus.
The Tradeoffs
Thinking the server is a simple dashboard
Trying to manually look up data by clicking through the Churnkey website's reports, which takes 15 minutes and requires exporting CSVs.
→
Use your AI client. Prompt it to run get_session_aggregates or list_retention_sessions. The agent pulls the summarized data and presents it directly in your chat, bypassing the UI entirely.
Over-complicating data access
Trying to combine 10 different manual steps—checking history, then updating contacts, then deleting data—by copying and pasting IDs between multiple tools.
→
Run the tools sequentially in your chat. Start by calling list_customer_retention_history for context, then use update_billing_contacts if needed, and finally run delete_customer_gdpr_data if the customer leaves.
Ignoring the scope of the tools
Asking the agent to analyze market sentiment or predict future pricing, assuming the server knows things outside of Churnkey's stored data.
→
The server only interacts with Churnkey. Stick to the defined tools. Use get_retention_session_details to pull facts about a session, not theories about the market.
When It Fits, When It Doesn't
Use this server if your workflow involves routine, repeatable actions on customer billing or retention data. You need to audit history, run mass updates, or enforce GDPR compliance, and you do this frequently enough that dashboard clicking is a bottleneck. Specifically, if you need to run get_session_aggregates to check trends, or use bulk_update_billing_contacts for maintenance, this is for you. Don't use it if you are just browsing data or need to manually compare data across multiple, unrelated systems. For simple read-only tasks that don't involve specific Churnkey data, use a general database querying tool instead. Remember, this tool is about actionable, structured customer lifecycle management.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Churnkey. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 8 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Checking customer churn reasons shouldn't require logging into a dashboard.
Today, if a founder wants to know why users are leaving, they have to log into the Churnkey platform. Then they click the reports tab. They filter by time period, then they run the analysis, and finally, they download a CSV file. It's a multi-step process that wastes time and requires manual interpretation.
With the Churnkey MCP Server, you simply tell your agent what you need. You run `get_session_aggregates`, and the agent immediately returns the analyzed data—the top reasons and the counts—right in your chat. You get the insight, not the spreadsheet.
Using Churnkey MCP Server: Update billing contacts from chat.
Manual billing updates mean logging into the customer account, finding the billing section, and typing in the new card details. If you have dozens of accounts, this is a full day of repetitive, error-prone clicking.
Now, you can use `bulk_update_billing_contacts`. Your agent takes the list of IDs and the new payment data, and executes the update in one go. The job is done. No dashboards, no manual clicks.
Common Questions About Churnkey MCP
How do I check a customer's retention history using Churnkey MCP Server? +
You use the list_customer_retention_history tool. This function retrieves every session for a specific customer, showing all the retention offers they were presented with over time.
Can I delete GDPR data using Churnkey MCP Server? +
Yes, use the delete_customer_gdpr_data tool. This function permanently removes all data for a specified customer ID, ensuring compliance with GDPR requests.
What is the difference between `list_retention_sessions` and `list_customer_retention_history`? +
list_retention_sessions shows all recent sessions across your whole user base. list_customer_retention_history focuses only on one customer ID's complete record.
Do I need to use `update_billing_contacts` for every single customer? +
No. If you need to update multiple accounts, use bulk_update_billing_contacts. The single-customer tool, update_billing_contacts, is only for one record at a time.
How do I use `get_session_aggregates` to analyze our overall churn trends? +
The get_session_aggregates tool provides grouped counts of session data. You can use this to find trends—for example, seeing which offer types or billing intervals caused the most cancellations this month.
What is the difference between `update_billing_contacts` and `update_billing_contacts`? +
The update_billing_contacts tool updates recovery contacts for a single, specific customer. If you need to update multiple accounts at once, use the bulk_update_billing_contacts tool instead.
Does the Churnkey MCP Server handle complex data types when I run `get_retention_session_details`? +
Yes, the tool retrieves detailed session metadata, including specific offer types (like 'Pause' or 'Discount') and the associated billing intervals. This helps give you a complete picture of the customer's interaction.
What should I do if my request to `list_retention_sessions` fails or returns an empty list? +
If the list is empty, it means no cancellation flow sessions were found recently. If the tool fails, check your API key and App ID in the Churnkey settings to confirm authentication.
Can I see the most common reason users are trying to cancel? +
Yes! Use the get_session_aggregates tool. The agent will return grouped data showing which reasons are being selected most frequently in your cancellation flows.
How do I update the billing contact for a customer whose payment failed? +
Use the update_billing_contacts tool. Provide the customer ID and the new contact details. This ensures Churnkey sends dunning and recovery emails to the right person.
Where do I find my Churnkey Data API Key and App ID? +
Log in to your Churnkey dashboard and navigate to Settings > Account. You can find your App ID and generate a Data API Key in the API section.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
FirstPromoter
Manage affiliates, track referrals, and handle rewards via AI agents with FirstPromoter.
HubSpot CRM
Search, create, and manage HubSpot contacts, companies, notes, tasks, and associations through natural conversation.
Albacross
B2B intent and reveal intelligence — identify anonymous website visitors and manage leads via AI.
You might also like
CoderPad
Manage technical interviews and assessments via CoderPad — create pads, track interview events, and audit the question bank directly from any AI agent.
Finch
Connect Finch to automate HRIS and Payroll integration — list employees, retrieve employment data, and manage pay statements directly from your AI agent.
Vonage Alternative
Manage your Vonage communications — send SMS and audit account data via AI.