How to integrate Kit MCP with Claude Code

Manage your Kit directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

Get started for freeGet a demo
Kit logoKit
Oauth2Api Key

Kit is a platform for creators and developers to automate tasks and publish apps on the Kit App Store. It helps streamline workflows so you can focus on what matters most.

42 Tools

Introduction

Manage your Kit directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Kit with

OpenAI Agents SDKClaude Agent SDKClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Kit to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

What is the Kit MCP server, and what's possible with it?

The Kit MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Kit account. It provides structured and secure access to your subscriber lists, tags, forms, and automations, so your agent can perform actions like managing subscribers, creating tags, updating custom fields, and handling broadcasts on your behalf.

  • Subscriber management and automation: Add new subscribers to forms, remove subscribers, or update their details to keep your audience lists accurate and engaged.
  • Custom field and tag creation: Automatically create, update, or delete custom fields and tags, making it easy to segment and personalize your communications.
  • Webhook and event setup: Set up or remove webhooks so your agent can listen for subscriber or purchase events and trigger automations as needed.
  • Broadcast and campaign control: Delete obsolete broadcasts or manage your messaging campaigns directly through your agent for streamlined outreach.
  • Account insights and configuration: Retrieve detailed account information, including plan details and primary contact, to keep your integrations and automations running smoothly.

Connecting Kit via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Kit) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Kit account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['kit'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http kit-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Kit. This URL will be used to connect Claude Code to Kit.

What's happening
  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Kit
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Kit MCP to Claude Code

bash
claude mcp add --transport http kit-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (kit-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Kit MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your kit-composio entry in the list
  • This confirms that Claude Code can now access Kit tools

If everything is wired up, you should see your kit-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Kit

The first time you try to use Kit tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Kit
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Kit authorization flow
  • Return to the terminal and start using Kit through Claude Code

Once authenticated, you can ask Claude Code to perform Kit operations in natural language. For example:

  • "Add new subscriber to my welcome form"
  • "Create a custom field for subscriber notes"
  • "Delete an outdated broadcast by its ID"

Complete Code

Here's the complete code to get you started with Kit and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['kit'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http kit-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Kit with Claude Code using Composio's MCP server. Now you can interact with Kit directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Kit operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Kit operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

TOOLS

Supported Tools

Every Kit action and event your agent gets out of the box.

Add Subscriber to Form

Add an existing subscriber to a form by their IDs.

Add Subscriber to Form by Email

Tool to add an existing subscriber to a form using their email address.

Create Broadcast

Tool to create a new broadcast (email campaign) to send to subscribers.

Create Custom Field

Tool to create a new custom field for subscriber data.

Create Subscriber

Tool to create a new subscriber or update an existing one (upsert).

Create Tag

Tool to create a new tag in the account.

Create Webhook

Creates a webhook subscription for real-time event notifications.

Delete Broadcast

Tool to delete a specific broadcast.

Delete Custom Field

Tool to delete a specific custom field.

Delete Subscriber

Unsubscribe a subscriber from all email communications by their ID.

Delete Tag

Tool to delete a tag by ID.

Delete Webhook

Tool to delete a webhook by ID.

Filter Subscribers

Tool to filter subscribers based on engagement criteria such as email opens, clicks, or delivery status.

Get Account

Tool to retrieve current account information.

Get Account Colors

Tool to retrieve list of colors associated with the account.

Get Broadcast

Tool to retrieve details of a specific broadcast by ID.

Get Broadcast Clicks

Tool to retrieve link click data for a specific broadcast by ID.

Get Broadcast Stats

Tool to retrieve statistics for a specific broadcast by ID.

Get Creator Profile

Tool to retrieve the creator profile information for the account.

Get Email Stats

Tool to retrieve email statistics for the account.

Get Growth Stats

Tool to retrieve growth statistics for the account over a date range.

Get Subscriber

Tool to retrieve a specific subscriber by their ID.

Get Subscriber Stats

Tool to retrieve email stats for a specific subscriber.

List Broadcasts

Tool to retrieve a paginated list of all broadcasts.

List Custom Fields

Tool to retrieve a paginated list of custom fields.

List Email Templates

Retrieve a paginated list of all email templates in the Kit account.

List Forms

Lists all forms in your Kit account with optional filtering and cursor-based pagination.

List Segments

Tool to retrieve a paginated list of segments.

List Sequences

Tool to retrieve a paginated list of all sequences.

List Subscribers

Tool to retrieve a list of subscribers.

List Subscribers For Form

Retrieves subscribers for a specific form by ID with optional filtering and cursor-based pagination.

List Tags

Retrieve a paginated list of all tags in the Kit account.

List Tag Subscribers

Tool to retrieve subscribers for a specific tag.

List Webhooks

Retrieve a paginated list of all webhooks configured in the Kit account.

Remove Tag From Subscriber

Tool to remove a tag from a subscriber using their subscriber ID.

Tag Subscriber

Tool to associate a subscriber with a specific tag by ID.

Tag Subscriber by Email

Assigns a tag to an existing subscriber using their email address.

Untag Subscriber by Email

Tool to remove a tag from a subscriber using their email address.

Update Account Colors

Tool to update the list of colors for the account.

Update Custom Field

Tool to update a custom field's label.

Update Subscriber

Tool to update an existing subscriber's information.

Update Tag

Tool to update a tag's name by ID.

FRAMEWORKS

How to build Kit MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Kit MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Kit MCP with Claude Agent SDK

Claude Cowork logo

Claude Cowork

Use Kit MCP with Claude Cowork

Codex logo

Codex

Use Kit MCP with Codex

OpenClaw logo

OpenClaw

Use Kit MCP with OpenClaw

Hermes logo

Hermes

Use Kit MCP with Hermes

CLI logo

CLI

Use Kit MCP with CLI

Google ADK logo

Google ADK

Use Kit MCP with Google ADK

LangChain logo

LangChain

Use Kit MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Kit MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Kit MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Kit MCP with LlamaIndex

CrewAI logo

CrewAI

Use Kit MCP with CrewAI

FAQ

Frequently asked questions

With a standalone Kit MCP server, the agents and LLMs can only access a fixed set of Kit tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Kit and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Kit tools.

Yes, absolutely. You can configure which Kit scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Kit data and credentials are handled as safely as possible.

Start with Kit.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Kit tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies