Kit MCP (Model Context Protocol) server is the universal connector between your Kit account and your favorite AI tool. Once it's connected, Claude, ChatGPT, Cursor, and other MCP-compatible AI assistants can read your Kit account and take actions on your behalf with simple questions and no coding required.
A few quick checks before you dive in:
Plans. Kit MCP is available on all paid Kit plans (Creator and Creator Pro). Free creators can still connect their AI client and see what's available, but running any tool will surface an upgrade prompt rather than executing the action.
What you'll need. A Kit account, plus a supported AI tool (see below). You don't need to be a developer.
You stay in control. Your AI tool only does what you ask, with the same permissions you have, so you can use your AI tool to schedule email broadcasts or delete subscribers. Please customize your AI tool permissions settings based on what you'd like for it to do.
You can review, pause, and revoke access at any time. More on this in Safety, permissions, and what your AI can see.
Already familiar with MCP? Skip ahead to Connect your AI tools or visit the MCP tools article to see what's available.
What is the Kit MCP?
MCP, short for Model Context Protocol, is an open standard that lets AI assistants safely connect to outside services. Think of it as a USB-C port for AI: any tool that speaks MCP can plug into any service that supports it.
The Kit MCP is the connector for your Kit account. It works the same way a USB-C port lets any cable plug into any device — Kit handles the messy bits underneath, and your AI assistant stays on the clean side.
Here's how the pieces fit together:
Your Kit account ⟶ Kit MCP server ⟶ Your AI assistant (Claude/ChatGPT)
Once connected, you can ask your AI to look things up, draft content, audit your audience, or take action on your behalf, all from inside the chat window or editor you already use.
What you can do with the Kit MCP
You ask your AI assistant a question or give it a task. It uses the Kit MCP to pull the data it needs, do the work, and report back. Here are some ideas:
Analyze your email marketing performance
"Summarize my last 5 broadcasts and their open rates."
"How has my open rate trended over the last 90 days?"
"What's my best-performing subject line format?"
Understand your audience
"Who are my most engaged subscribers in the last 30 days?"
“Where are most of my recent subscriber growth coming from?”
“Which subscribers have purchased from me more than once?”
Manage your marketing admin
"Which tags have grown the most this month? Suggest any duplicates I could merge."
“Which tags have not had any activity? Suggest any I can archive.”
“"Find my most engaged subscribers, tag them VIP, and draft a broadcast just for them."
The power lies in stitching actions together — for example, importing subscribers from an external source, tagging them, drafting a broadcast, targeting the subscribers, and sending it. All through a conversation with an AI assistant. No UI clicks required.
Connect the Kit MCP to your AI tool
Connecting Kit to an AI tool takes about 60 seconds. The flow is the same across every supported MCP-compatible tool; the only difference is where you paste the URL.
How connecting works (read this first)
Whatever AI tool you use, the flow is the same:
In your AI tool you use, go to add a custom connector.
In the pop up, you'll add the following as a new MCP server (the exact menu name varies; see your AI tool below):
Your AI tool opens a Kit sign-in page in your browser.
Review the requested permissions and click Allow.
You'll see a "Connected to Kit" confirmation page, then jump back to your AI tool. You're done!
Heads up: Some desktop AI tools (like Cursor and Claude Desktop) use custom-scheme links to send you back into the app after sign-in. If you do, that's expected—click the button to finish.
Who has access to the Kit MCP?
Once the MCP is enabled, any additional users on your Kit account will also be able to connect their own AI client with the same read or write access they have today as editors. Please make sure you review who has access to your account at all times.
Set up your AI tool
Claude
Connect the Kit MCP to Claude:
Open Claude Desktop.
Go to Customize → Connectors (or open claude_desktop_config.json directly — see below) → + Add custom connector:
Add a new custom connector with the name as Kit and the URL
https://app.kit.com/mcp:
Save and restart Claude Desktop. A browser window will open for sign-in.
Sign in to Kit, click Allow, and return to Claude Desktop.
If you'd rather edit the config file by hand, open it at:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
…and add:
{
"mcpServers": {
"kit": {
"url": "https://app.kit.com/mcp"
}
}
}A one-click marketplace listing for Claude is on the way. For now, see Claude's custom-connector docs.
ChatGPT
Connect the Kit MCP to ChatGPT:
This can only be configured on the web, not via the desktop app.
In ChatGPT, ensure Developer mode is turned on. To do this, open Settings → Apps → Advanced Settings and toggle on Developer mode.
Click the Create app button at the top. ;
Name - we recommend using
KitMCP Server URL -
https://app.kit.com/mcp.Authentication - OAuth.
Check the I understand and want to continue box and press the Create button.
ChatGPT will redirect you to sign in and authorize access to Kit. Select your account and click Authorize & Accept Terms.
Return to ChatGPT — Kit will appear in your enabled Apps list. Use
@Kitto add it to your chat context to use it.
ChatGPT supports remote MCP servers via the Apps feature on Plus, Team, and Enterprise plans. A one-click directory listing is on the way. See ChatGPT Apps for general guidance.
Cursor
Connect the Kit MCP to Cursor:
Open Cursor.
Go to Settings → Tools & Integrations → MCP Tools.
Click Add server and paste
https://app.kit.com/mcp.Save. Cursor opens a browser window for sign-in.
Sign in to Kit, click Allow, and return to Cursor.
If you prefer to edit your config file directly, here's the snippet:
{
"mcpServers": {
"kit": {
"url": "https://app.kit.com/mcp"
}
}
}Use the key name kit for this MCP. If you also use the Kit Developer Docs MCP, use kit-docs for that one to keep the labels clean.
For Cursor's general MCP documentation, see Cursor's MCP docs.
For other AI tool instructions, check your tool's MCP documentation:
If you run into trouble with an unlisted client, drop us a note via the support widget. We're tracking which creators are using which clients and will add specific guides as we go.
What your AI can do
Once Kit MCP is connected, your AI assistant has access to a set of available tools. These are the individual actions it can take on your behalf. Tools are how MCP clients describe their capabilities to AI models and Kit currently has 65+ available tools.
Here's what it can do:
Read your account
List, search, and look up anything in your Kit account: subscribers, tags, segments, sequences, broadcasts, forms, custom fields, posts, purchases, account stats, growth trends, and engagement reports.
Manage your audience
Create, update, tag, untag, segment, and unsubscribe your subscribers. Apply tags in bulk. Add subscribers to forms or sequences. Update a custom field across a filtered group.
Compose and send
Draft and edit broadcasts, and (with your explicit confirmation) schedule sends. Your AI can edit subject lines, body copy, and audience filters, just like you would in Kit.
Automate and integrate
Manage webhooks, custom fields, email templates, and the connective tissue that connects Kit to other tools in your stack.
Where to see the live catalogue
Your AI client lists the available tools when it first connects, and it'll always reflect the current surface as new tools ship. If you want a quick tour, just ask your AI: "What Kit tools do you have access to?" or check the MCP tools article for an up-to-date list.
Kit MCP Prompt library
Once you've connected the Kit MCP, start here to see what you can do with your Kit connected to your AI tool.
Prompt templates are pre-built workflows that come with the Kit MCP. They're shortcuts to common, high-value things that creators want to do that we’ve tested and ready to run.
Think of them as a starter pack. Instead of writing your own prompt from scratch and explaining your goal step by step, you pick a template, and your AI takes it from there.
Why they're useful
Faster activation. You don't have to know what to ask first. Pick a template, run it, see the output.
Built using Kit's expertise. They're written to surface what's worth knowing: engagement metrics that matter, segments worth a closer look, common cleanup wins.
A great starting point. Run a template, then keep the conversation going to dig deeper, ask follow-ups, or change direction.
What's in the prompt library
The library covers the everyday workflows you care about: analyzing your audience and content performance, drafting campaigns and welcome flows, auditing your tags and list health, and re-engaging quieter subscribers. New templates will continue to be added based on the questions you want to ask.
How to use a MCP prompt
Open any of the prompts that seem of interest to you. You'll see a deeper dive into what the MCP prompt is designed to do.
All you have to do run an MCP prompt is:
Click on an MCP prompt that's interesting to you
Click on the Copy button under the prompt.
Paste into a new chat in your AI tool.
Hit enter and wait for the results!
In supported AI tools (like Claude Desktop and Cursor), prompt templates appear in the slash-command menu. Type / and you'll see them listed. Pick one and press enter to run it. In other AI tools, just paste the prompt name into the chat and your AI will pick it up.
Safety, permissions, and what your AI can see
Kit MCP doesn't give your AI client any new powers over your account. Anything an AI tool can do here is something you could already do yourself in Kit. You can see, pause, or revoke it at any time.
The MCP builds on what is already available in Kit or via the API. There are three layers of protection:
What Kit does. Every tool carries a risk tag (read, write, or destructive). Your AI client uses those tags to decide when to pause and ask before acting. These are built into prompts to ensure they are adhered to.
What you control. Reading data is silent. Writing (e.g. tagging a subscriber) shows a confirmation in your AI tool. For destructive or open-world actions (sending a broadcast, deleting a sequence, unsubscribing a subscriber, firing a webhook), Kit MCP doesn't run the action directly — it returns a deep link into Kit and the write only fires when you click Confirm inside the Kit app. For greater security, please check your AI tool's permission settings.
What you can undo. If you make a mistake, first ask your AI client to undo the action; it may be able to rectify it itself. However, the best way to prevent this is to ensure you are clear on what your AI client is doing before approval - all write/delete actions require explicit approval.
On rate limits. Kit MCP is rate-limited per AI client connection with enough headroom for any normal creator workflow — if you hit it, your AI will pause and retry automatically.
Troubleshooting & FAQ
I can't connect. What should I do?
Try these in order:
Browser pop-ups. The OAuth flow opens a new tab. If your browser is blocking pop-ups for
app.kit.com, allow them and try again.The right URL. Make sure you've pasted
https://app.kit.com/mcpexactly — no trailing slash or extra path.Restart the client. Some clients only pick up new MCP servers after a restart.
If none of those work, reach out via the support widget with your client name and a screenshot of the error.
My AI client is stuck on "Exchanging token". What now?
Close and reopen the client. If it persists, revoke access from the AI Setup page in Kit and reconnect — the OAuth flow restarts cleanly.
My AI client isn't listed above. Can I still use it?
Any client that supports remote MCP servers can connect to Kit. Check their help center or ask the client itself how to set up custom MCP connections, using https://app.kit.com/mcp as the MCP server URL.
If you run into a snag, let us know via the support widget. We want to expand this list as the ecosystem grows.
How do I disconnect or revoke access?
Two ways:
In Kit. Go to your MCP settings page in the Kit app, find the client you want to disconnect, and click Revoke access. This kills the connection on Kit's side immediately.
In your AI tool. Most clients let you remove an MCP server from their settings menu. Removing it there will stop your client from sending requests, but the access token stays valid until you also revoke it in Kit. We recommend revoking from Kit for completeness.
I revoked access mid-session . What will happen?
Your AI will get a "connection lost" style error on its next call. Reconnect via the steps in Connect your AI client and you're back.
Does this work on the Free plan?
Free creators can connect their AI client and inspect the available tools, but running any tool surfaces an upgrade prompt rather than executing. Kit MCP requires a Creator or Creator Pro plan to actually use — upgrade in Settings → Billing if you'd like to.
Why did my AI say it hit a rate limit?
Each AI tool connection is allowed 120 requests per minute. You'd typically only hit it during bulk operations (e.g. tagging tens of thousands of subscribers in a single conversation).
If you do hit it, most AI clients will pause and retry automatically. If you keep hitting it, ask your AI to slow down or to batch the work over multiple steps.
Can my AI delete things by accident?
Your AI should pause and ask for confirmation before it actually fires. However, if you have set your client to accept all edits, it may make changes on your behalf, so it is important to be clear with your AI client of choice when you don't want it to update items in your account for safety.
You can also revoke a client's access entirely from the AI Setup page. See Safety, permissions, and what your AI can see.
What if I'm also running the Developer Docs MCP?
Kit publishes two MCP servers. They do different things:
Server | URL | What it does |
Kit MCP (this one) | Read and act on your Kit account | |
Kit Developer Docs MCP | Search Kit's developer documentation. Learn more at Kit's developer docs here. |
If you use both, name them kit and kit-docs in your client config, so the labels don't clash.