Connect ConvertKit to Claude Code

Let Claude tag subscribers and draft broadcasts in ConvertKit. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect ConvertKit to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect ConvertKit, you add a ConvertKit MCP server: a small hosted service that exposes ConvertKit's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own ConvertKit account. No API keys pasted into config files.

claude mcp add --transport http convertkit https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in ConvertKit once connected?

Full read-write ConvertKit access lets Claude tag and untag subscribers, add them to sequences, draft and update broadcasts, manage custom fields, and queue a send once you approve it. The list hygiene and campaign prep that used to mean clicking through the dashboard happen where your subscribers already live.

Add or remove tags on subscribers based on a query you describe
Add people to a sequence based on a query you describe
Draft a broadcast with subject and body for your review
Update custom fields on a subscriber record
Create a new tag and apply it to a segment
Add subscribers to an existing form
Queue an approved broadcast to send

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same ConvertKit access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the ConvertKit API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when ConvertKit changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build ConvertKit connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same ConvertKit connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own ConvertKit account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on ConvertKit's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to ConvertKit?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the ConvertKit account it signs in with. Revoking access is one click in ConvertKit.

More on the ConvertKit connector

ConvertKit connector for claude.ai Braze + Claude Code Iterable + Claude Code Customer.io + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us