Koskamo

Churnkey MCP

An official MCP server provided by Churnkey that allows AI agents to interact with the Churnkey retention platform. It enables users to read retention metrics, analyze payment recovery performance, build and manage cancel flows, and publish changes to live campaigns, all secured via OAuth 2.1 with role-scoped permissions.

Visit Churnkey

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Churnkey MCP logo, by ChurnkeyVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-07Operated by Churnkey
You need:A workspace admin turns on MCP Access for your user in Churnkey → Team
MCP endpoint (Streamable HTTP)
https://mcp.churnkey.co/mcp
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to churnkey.co ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Analyze payment recovery performance by decline reason
  • Build and manage in-app cancel flows
  • Run cohort analysis on save rates by plan
  • Publish changes to live retention campaigns

Source and maintenance

Vendor evidenceRegistry 2.4.1
mcp-registry: co.churnkey/churnkey@2.4.1Source repositoryProject website
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-09: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
408 ms
95th percentile latency
408 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 408 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http churnkey-mcp https://mcp.churnkey.co/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add churnkey-mcp --url https://mcp.churnkey.co/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable churnkey-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "churnkey-mcp": {
      "url": "https://mcp.churnkey.co/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "churnkey-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.churnkey.co/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start churnkey-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "churnkey-mcp": {
      "type": "http",
      "url": "https://mcp.churnkey.co/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http churnkey-mcp https://mcp.churnkey.co/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.churnkey.co/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "churnkey-mcp": {
      "serverUrl": "https://mcp.churnkey.co/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Churnkey MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 1,402

Do you run Churnkey MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing