2,500+ MCP servers ready to use
Vinkius

Churnkey MCP Server for AutoGen 8 tools — connect in under 2 minutes

Built by Vinkius GDPR 8 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Churnkey as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="churnkey_agent",
            tools=tools,
            system_message=(
                "You help users with Churnkey. "
                "8 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())
Churnkey
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Churnkey MCP Server

Connect your Churnkey account to any AI agent and take full control of your customer retention and cancellation automation through natural conversation. Streamline how you handle churn and recover failed payments.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Churnkey tools. Connect 8 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

What you can do

  • Session Oversight — List and retrieve details for all customer cancellation flow sessions natively
  • Aggregation Intelligence — Access grouped session counts to identify trends in churn reasons flawlessly
  • Recovery Logistics — Update and manage billing recovery contacts for specific customers securely
  • Retention Deep-Dives — List all cancellation sessions for a specific customer to understand their history flawlessly
  • Compliance Management — Access and delete customer data for GDPR requests directly within your workspace flawlessly
  • Data Logistics — Retrieve session metadata including offer types (discounts, pauses) and billing intervals flawlessly

The Churnkey MCP Server exposes 8 tools through the Vinkius. Connect it to AutoGen in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Churnkey to AutoGen via MCP

Follow these steps to integrate the Churnkey MCP Server with AutoGen.

01

Install AutoGen

Run pip install "autogen-ext[mcp]"

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

04

Explore tools

The workbench discovers 8 tools from Churnkey automatically

Why Use AutoGen with the Churnkey MCP Server

AutoGen provides unique advantages when paired with Churnkey through the Model Context Protocol.

01

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Churnkey tools to solve complex tasks

02

Role-based architecture lets you assign Churnkey tool access to specific agents. a data analyst queries while a reviewer validates

03

Human-in-the-loop support: agents can pause for human approval before executing sensitive Churnkey tool calls

04

Code execution sandbox: AutoGen agents can write and run code that processes Churnkey tool responses in an isolated environment

Churnkey + AutoGen Use Cases

Practical scenarios where AutoGen combined with the Churnkey MCP Server delivers measurable value.

01

Collaborative analysis: one agent queries Churnkey while another validates results and a third generates the final report

02

Automated review pipelines: a researcher agent fetches data from Churnkey, a critic agent evaluates quality, and a writer produces the output

03

Interactive planning: agents negotiate task allocation using Churnkey data to make informed decisions about resource distribution

04

Code generation with live data: an AutoGen coder agent writes scripts that process Churnkey responses in a sandboxed execution environment

Churnkey MCP Tools for AutoGen (8)

These 8 tools become available when you connect Churnkey to AutoGen via MCP:

01

bulk_update_billing_contacts

Update billing recovery contacts for multiple customers at once

02

delete_customer_gdpr_data

Delete all data for a customer for GDPR compliance

03

get_customer_gdpr_data

Access all data stored for a customer for GDPR compliance

04

get_retention_session_details

Get details for a specific cancellation session

05

get_session_aggregates

Retrieve grouped session counts

06

list_customer_retention_history

List all cancellation sessions for a specific customer

07

list_retention_sessions

List cancellation flow sessions

08

update_billing_contacts

Update recovery contacts for a specific customer

Example Prompts for Churnkey in AutoGen

Ready-to-use prompts you can give your AutoGen agent to start working with Churnkey immediately.

01

"Show me the last 5 cancellation sessions in Churnkey."

02

"What are the session aggregates for this month?"

03

"List all retention sessions for customer 'cust_123'."

Troubleshooting Churnkey MCP Server with AutoGen

Common issues when connecting Churnkey to AutoGen through the Vinkius, and how to resolve them.

01

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Churnkey + AutoGen FAQ

Common questions about integrating Churnkey MCP Server with AutoGen.

01

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Churnkey tools during their conversation turns.
02

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
03

Does AutoGen support human approval for tool calls?

Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.

Connect Churnkey to AutoGen

Get your token, paste the configuration, and start using 8 tools in under 2 minutes. No API key management needed.