Skip to main content

Integration walkthrough · Updated 2026-05-22

Kit MCP + Claude: two integrations, two jobs — the honest setup walkthrough

Kit ships an official MCP server for its API documentation at developers.kit.com/mcp/kit-developer-docs-mcp. For managing your Kit account from Claude — subscribers, broadcasts, sequences — you need a community-built MCP at github.com/aplaceforallmystuff/mcp-kit. This walkthrough covers both setups, the operator hygiene that keeps the credentials clean, and the honest framing for when each one is the right tool.

Want to try Kit?

Kit is the creator-tier-favorite email platform — product depth is the real wedge

Official MCP today is docs only. Community account-data MCP works but needs self-hosting. Vendor-hosted account-data MCP likely coming.

Start with Kit →Affiliate link — StackSwap earns a commission if you sign up for Kit. We only partner with tools we'd recommend anyway.

Path A: Kit Developer Docs MCP (official, easy)

Use this path when you want LLM-assisted Kit API documentation lookup — typical use is partners or developers building integrations against Kit's API.

Setup steps:

  • Claude Desktop / claude.ai: Settings → Connectors → Add custom MCP. Endpoint: developers.kit.com/mcp/kit-developer-docs-mcp. No API key required.
  • Claude Code: add the server to your workspace .mcp.json or project config with the same endpoint URL.
  • Smoke test: "Using the Kit docs MCP, show me the endpoint for listing subscribers." If you see API documentation in response, the connection is healthy.

Total setup time: about 2 minutes. No credential to manage, no account required.

Path B: Community account-data MCP (self-hosted, real-account)

Use this path when you want chat-driven Kit account management — sending broadcasts, querying subscribers, managing sequences from Claude.

Setup steps:

  • Clone the repo. github.com/aplaceforallmystuff/mcp-kit. Follow the repo's README for the current setup process (Node.js typical).
  • Generate a Kit API key. In your Kit account: Settings → API Keys. Name it explicitly for AI use ("Claude integration — Nick"). Paste it into the MCP server's config (typically an env var).
  • Deploy somewhere reachable. Locally for desktop use (run the server on your machine), or a small VPS ($5/mo Hetzner is standard) for always-on access.
  • Pin to a specific commit for production stability. Community-maintained schemas can shift; pinning means you control when you adopt changes.
  • Configure Claude: Settings → Connectors → Add custom MCP, point at your self-hosted endpoint. For Claude Code, add to your workspace .mcp.json.
  • Smoke test: "Using the community Kit MCP, list my recent broadcasts." If you see your actual broadcasts, the connection works.

Total setup time: 30-60 minutes for first-time setup including any troubleshooting. Meaningfully more involved than vendor-hosted MCPs like Brevo's — that's the honest cost of community-tier tooling.

The 5 workflows that earn the install

1. Draft and send broadcasts from chat (community MCP)

"Draft a broadcast for our 'paid newsletter — week 8' segment with the lesson topic and a soft promo for the upcoming course. Schedule it for Saturday 9 AM Eastern." LLM writes; community MCP sends; you confirm via the client's confirmation UX.

2. Subscriber query and segmentation (community MCP)

"Show me subscribers tagged 'paid' who haven't opened the last 3 emails. Add a 'reactivation' tag to that group." Chat-driven analysis + bulk tag operations.

3. Sequence management (community MCP)

"Move all subscribers currently on step 5 of the welcome sequence to step 7." Useful when you've revised a sequence and need to fast-forward existing subscribers.

4. API integration prototyping (docs MCP)

"I'm building a Zapier-alternative integration with Kit. Walk me through the auth flow and show me a Node.js example for sending a broadcast." The docs MCP returns API content; the LLM generates working code grounded in the actual docs.

5. Broadcast performance summarization (community MCP)

"Pull performance data for my last 5 broadcasts. Which had the highest engagement? What's different about the winning ones?" Replaces the dashboard-walking session.

Operator advice for 2026

Three honest points:

  • Set expectations. Kit's official MCP today is the docs MCP — useful for builders, not for operators. If you're evaluating Kit specifically because you want chat-driven email management, know that you'll be running a community MCP self-hosted to get there.
  • Pin community schemas. Community- maintained code can shift; pin to a specific commit for production stability and control when you adopt changes.
  • Watch for an official Kit account-data MCP. Kit shipping the docs MCP is a signal they're investing in the protocol. An official account-data MCP is the natural next step — when (or if) that ships, the self-hosting overhead goes away.

Where StackSwap MCP fits

Kit's MCPs (either one) expose Kit-specific data. The cross-vendor question — "should we keep Kit or move to Brevo as our operational MCP needs grow" — sits at a different layer.

That's where StackSwap MCP slots in. ~400 GTM tools, cost models, overlap pairs. Load it alongside whichever Kit MCP you're using.

Want to try Kit?

Kit is the right pick for creators who value product depth over MCP polish

Official docs MCP today, community account-data MCP available, vendor-hosted account MCP likely coming.

Start with Kit →Affiliate link — StackSwap earns a commission if you sign up for Kit. We only partner with tools we'd recommend anyway.

FAQ

Two different setups depending on what you want. (1) Kit Developer Docs MCP (official): in Claude Desktop or claude.ai, Settings → Connectors → Add custom MCP, point at developers.kit.com/mcp/kit-developer-docs-mcp. No auth required; it's an open docs surface. Use it for API documentation lookup. (2) Community account-data MCP (github.com/aplaceforallmystuff/mcp-kit): clone the repo, self-host the server, generate a Kit API key in your Kit account settings, configure your MCP client to point at your self-hosted endpoint with the API key. Use it for managing subscribers, broadcasts, sequences from Claude.

The Kit Developer Docs MCP doesn't require a Kit account at all — it's an open docs surface. The community account-data MCP requires a Kit API key, which is on Kit's paid tiers (Creator at $9/mo for up to 300 subscribers, Creator Pro at $25/mo for broader feature access including API). For most creators evaluating Kit + Claude, you're already on a paid Kit tier for the email-tool reasons; the API key comes along for the ride.

Five use cases for the docs MCP: (1) endpoint lookup — 'how do I list subscribers via Kit\'s API, what parameters'; (2) auth flow walkthrough — 'walk me through OAuth vs API-key for Kit'; (3) code-example generation in your target language for common operations; (4) webhook payload reference; (5) cross-API comparison when evaluating integration approaches. The docs MCP is genuinely useful for partners and integration builders, but it doesn't manage your Kit account data — for that, you need the community MCP.

Five workflows on the account-data side: (1) draft and send a broadcast from chat; (2) query subscribers — 'show me subscribers tagged "founders" who haven\'t opened the last 3 emails'; (3) bulk tag operations; (4) sequence management — pause, resume, modify subscribers' position; (5) analytics queries on broadcast performance. Self-hosted, so the deployment overhead is on you — for creators willing to run their own MCP, it's the viable path to chat-driven Kit operations until Kit ships an official account-data MCP.

Clone github.com/aplaceforallmystuff/mcp-kit, follow the repo's setup instructions (Node.js typically, env-var-based config for the Kit API key), deploy it somewhere reachable from your Claude client (locally for desktop use, or a small VPS like a $5/mo Hetzner box for always-on access). Pin to a specific commit for production stability — community-maintained schemas can shift. The setup is more involved than vendor-hosted MCPs like Brevo's; budget 30-60 minutes for first-time setup including troubleshooting.

Yes — same operator hygiene as every MCP credential. Create a dedicated Kit API key for Claude use, named explicitly. Don't paste your primary API key into the community MCP config if you also use that key elsewhere; rotation and revocation get simpler with isolated keys. The LLM inherits whatever the key can do — Kit's API permissions are workspace-scoped, so the blast radius is the workspace.

Honest framing: Kit ships an official MCP for API docs (useful for developers building integrations), and the community ships an account-data MCP (useful for operators managing subscribers and broadcasts from chat). Both are real; neither is fully equivalent to Brevo's mcp.brevo.com or Mailchimp's official MCP tooling. If you're a creator already on Kit for the product-depth reasons (paid newsletters, landing pages, creator-friendly UX), the community MCP is workable. If you're shopping for SMB email and vendor-hosted account-data MCP is a deciding factor, Brevo or ActiveCampaign offer that today. Kit may close the gap; today, this is the landscape.

Yes to all three — they all support custom MCP connectors. The Developer Docs MCP is reachable as a standard custom MCP from any Claude surface. The community account-data MCP requires you to point your Claude client at your self-hosted endpoint; Claude Code is often the most natural surface here because the project-level .mcp.json config makes it easy to manage the connection alongside other dev-tool MCPs. Claude Desktop and claude.ai work too but require manually adding the connector with the self-hosted endpoint URL.

Related reading

Canonical URL: https://stackswap.ai/kit-mcp-claude-integration. Disclosure: StackSwap is a Kit affiliate.