# Churnkey MCP server

> Read and manage Churnkey cancel flows, retention metrics, and payment recovery from your AI assistant.

- Listing: https://mcp.tc/i/churnkey
- Connect: use the server's own URL `https://mcp.churnkey.co/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Data & Analytics](https://mcp.tc/c/analytics)
- Vendor: Churnkey
- Homepage: <https://churnkey.co/feature/mcp>
- Docs: <https://docs.churnkey.co/data-integrations/mcp>
- Repository: <https://github.com/churnkey/sdk>

## About

Connects an AI assistant to a Churnkey account. It can read retention data such as cancel flow sessions, metrics and adaptive offers, and it can edit cancel flow blueprints and adaptive offers. The OAuth scopes also cover Stripe settings and DNS settings.

It runs as a hosted streamable HTTP endpoint at https://mcp.churnkey.co/mcp. Users sign in with OAuth, and access is limited to the scopes granted to their role. A local @churnkey/mcp package in the vendor's SDK repository uses a Data API key instead.

## What it can do

- Read cancel flow blueprints and sessions
- Edit cancel flow blueprints
- Read cancel flow retention metrics
- Read and edit adaptive offers
- Read and edit Stripe settings
- Read and edit DNS settings

## Example prompts

- "Show cancel flow metrics for the last 30 days."
- "List recent cancel flow sessions and why customers left."
- "Update my cancel flow blueprint to add a pause offer."
- "Which adaptive offers are active right now?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http churnkey https://mcp.churnkey.co/mcp
```

2. Start Claude Code, type `/mcp`, pick **churnkey** and choose **Authenticate**. A browser window opens for the Churnkey sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Churnkey** and paste this URL:

```url
https://mcp.churnkey.co/mcp
```

3. Click **Add**, then **Connect**, and sign in when Churnkey asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Churnkey&connectorUrl=https%3A%2F%2Fmcp.churnkey.co%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.churnkey.co/mcp` and click **Add**.

3. Click **Connect** and sign in when Churnkey asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://mcp.churnkey.co/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Churnkey to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=churnkey&config=eyJ1cmwiOiJodHRwczovL21jcC5jaHVybmtleS5jby9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "churnkey": {
      "url": "https://mcp.churnkey.co/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=churnkey&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.churnkey.co%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"churnkey","type":"http","url":"https://mcp.churnkey.co/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "churnkey": {
      "type": "http",
      "url": "https://mcp.churnkey.co/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "churnkey": {
      "serverUrl": "https://mcp.churnkey.co/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add churnkey --url https://mcp.churnkey.co/mcp
codex mcp login churnkey
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.churnkey]
url = "https://mcp.churnkey.co/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http churnkey https://mcp.churnkey.co/mcp
```

Then, inside Gemini CLI, run `/mcp auth churnkey` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "churnkey": {
      "type": "http",
      "url": "https://mcp.churnkey.co/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.churnkey.co/mcp`.

## Details

- Server version: 2.3.0
- Last checked: 2026-10-07 (reachable, asks for credentials)
- Listed: 2026-10-06
- Updated: 2026-10-06

---
Source: https://mcp.tc/i/churnkey (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report