Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developers.kit.com/llms.txt

Use this file to discover all available pages before exploring further.

The Kit MCP is a remote MCP server that exposes a creator’s Kit account — subscribers, sequences, broadcasts, tags, segments, and more — to MCP-compatible AI clients. Where the Kit Developer Docs MCP gives your agent read-only access to these docs, the Kit MCP gives an AI client the ability to read and write live account data on the creator’s behalf. 
https://app.kit.com/mcp
Add this URL as a custom connector in your MCP-compatible AI client. Step-by-step instructions for each major client live in the help centre guide.
Canonical guide. The complete setup and usage documentation for the Kit MCP lives in the Kit help centre: Using the Kit MCP. This page is a developer-oriented brief — for step-by-step setup, head to the help centre.

​
Who it’s for

  • Creators using AI clients (Claude Desktop, ChatGPT, Cursor, and others) to manage their Kit account through natural language.
  • Developers building tools, scripts, or workflows on top of an authenticated creator session — for example, internal automations or AI-driven assistants that act against a single account.
  • Kit App Store builders who want to dogfood agentic flows during development, or prototype AI features against a real account before formalising them as an app.

​
Availability

The Kit MCP is available on all paid Kit plans (Creator and Creator Pro).

​
What it can do

The Kit MCP is essentially a one-to-one mapping of Kit’s v4 API surface — every endpoint in the API reference is exposed as an MCP tool. That covers, for example:
  • Read account data — subscribers, sequences, broadcasts, tags, segments, custom fields, and account-level info.
  • Manage subscribers — create, update, tag, untag, and segment.
  • Send and draft broadcasts — compose, schedule, and send to filtered audiences.
For the full tool catalogue, see the help centre guide.

​
Safety

Every tool the Kit MCP exposes carries an annotation — readOnlyHint, destructiveHint, idempotentHint, or openWorldHint — that supported AI clients use to decide when to ask for confirmation. Read operations run without prompts; write operations apply appropriate safety layers; destructive or external actions (sending broadcasts, deleting data) always require explicit user confirmation.

​
Authentication

The Kit MCP authenticates via OAuth on behalf of the creator. On first connect, your AI client opens a Kit authorization flow — the creator signs in and grants access — and the resulting access token is scoped to that creator’s account. Tokens use the same OAuth model as Kit App Store apps; see Authentication for the underlying flow, and the help centre guide for client-side setup. Requests are rate-limited to 120 per minute per token.

​
How it relates to other Kit developer surfaces

  • Kit API v4 — programmatic, code-driven access. Use this when you’re building an app, script, or integration. The Kit MCP sits on top of the API as an interface layer for less technical creators, letting them work with the same capabilities through an AI client without writing API calls directly.
  • Kit Developer Docs MCP — read-only access to these developer docs for your AI coding agent. No account access.
If you run into issues or have feedback on the Kit MCP from a developer perspective, reach out via the Kit Developer Community. For creator-side support, the help centre guide is the place to start.