How to integrate Kit MCP with CrewAI

This guide walks you through connecting Kit to CrewAI using the Composio tool router. By the end, you'll have a working Kit agent that can add new subscriber to your welcome form, create a custom field for subscriber notes, delete an outdated broadcast by its id through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Kit account through Composio's Kit MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

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

This guide walks you through connecting Kit to CrewAI using the Composio tool router. By the end, you'll have a working Kit agent that can add new subscriber to your welcome form, create a custom field for subscriber notes, delete an outdated broadcast by its id through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a Kit account through Composio's Kit MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Kit with

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Kit connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Kit
  • Build a conversational loop where your agent can execute Kit operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

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 step08 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Kit connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Kit via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
5

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Kit MCP URL
6

Create a Composio Tool Router session for Kit

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["kit"])

url = session.mcp.url
What's happening:
  • You create a Kit only session through Composio
  • Composio returns an MCP HTTP URL that exposes Kit tools
7

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
8

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

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

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["kit"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Kit through Composio's Tool Router. The agent can perform Kit operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations
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.

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. CrewAI 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