# How to integrate Kit MCP with OpenAI Agents SDK

```json
{
  "title": "How to integrate Kit MCP with OpenAI Agents SDK",
  "toolkit": "Kit",
  "toolkit_slug": "kit",
  "framework": "OpenAI Agents SDK",
  "framework_slug": "open-ai-agents-sdk",
  "url": "https://composio.dev/toolkits/kit/framework/open-ai-agents-sdk",
  "markdown_url": "https://composio.dev/toolkits/kit/framework/open-ai-agents-sdk.md",
  "updated_at": "2026-05-12T10:16:50.869Z"
}
```

## Introduction

This guide walks you through connecting Kit to the OpenAI Agents SDK 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 OpenAI Agents SDK 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

- [Claude Agent SDK](https://composio.dev/toolkits/kit/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/kit/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/kit/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/kit/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/kit/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/kit/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/kit/framework/cli)
- [Google ADK](https://composio.dev/toolkits/kit/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/kit/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/kit/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/kit/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/kit/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/kit/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Install the necessary dependencies
- Initialize Composio and create a Tool Router session for Kit
- Configure an AI agent that can use Kit as a tool
- Run a live chat session where you can ask the agent to perform Kit operations

## What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.
Key features include:
- Hosted MCP Tools: Connect to external services through hosted MCP endpoints
- SQLite Sessions: Persist conversation history across interactions
- Simple API: Clean interface with Agent, Runner, and tool configuration
- Streaming Support: Real-time response streaming for interactive applications

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

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `KIT_ADD_SUBSCRIBER_TO_FORM` | Add Subscriber to Form | Add an existing subscriber to a form by their IDs. This action associates a subscriber with a form in Kit. The subscriber must already exist in your Kit account (use KIT_LIST_SUBSCRIBERS to find them). The form must also exist (use KIT_LIST_FORMS to find valid form IDs). Returns HTTP 201 if the subscriber is newly added to the form, or HTTP 200 if they were already associated with the form. Both cases are considered successful operations. Important: This action requires both form_id and subscriber_id (aliased as 'id' in requests). An optional referrer URL can be provided for tracking purposes and will have its UTM parameters automatically parsed. |
| `KIT_ADD_SUBSCRIBER_TO_FORM_BY_EMAIL` | Add Subscriber to Form by Email | Tool to add an existing subscriber to a form using their email address. Use when you know the subscriber's email but not their ID. The subscriber must already exist in your Kit account before adding them to a form. Returns HTTP 201 if the subscriber is newly added to the form, or HTTP 200 if they were already associated with the form. |
| `KIT_CREATE_BROADCAST` | Create Broadcast | Tool to create a new broadcast (email campaign) to send to subscribers. Use when you need to draft, schedule, or immediately publish an email broadcast. To save as draft, set send_at to null; to schedule, provide a future send_at timestamp; to publish to web, set public to true. |
| `KIT_CREATE_CUSTOM_FIELD` | Create Custom Field | Tool to create a new custom field for subscriber data. Use when you need to store extra attributes for subscribers. |
| `KIT_CREATE_SUBSCRIBER` | Create Subscriber | Tool to create a new subscriber or update an existing one (upsert). If a subscriber with the provided email address does not exist, creates one. If already exists, updates the first name. |
| `KIT_CREATE_TAG` | Create Tag | Tool to create a new tag in the account. Use when you need a custom label to segment subscribers. Use after confirming tag uniqueness to avoid duplicates. Example: "Create a tag called 'VIP' for premium customers." |
| `KIT_CREATE_WEBHOOK` | Create Webhook | Creates a webhook subscription for real-time event notifications. Use this to receive HTTP POST notifications when subscriber events (activate, unsubscribe, form subscribe, tag add/remove, link clicks, etc.) or purchase events occur in your Kit account. |
| `KIT_DELETE_BROADCAST` | Delete Broadcast | Tool to delete a specific broadcast. Use when you need to permanently remove a broadcast by ID (after confirming the ID). Example prompt: "Delete broadcast with ID 123" |
| `KIT_DELETE_CUSTOM_FIELD` | Delete Custom Field | Tool to delete a specific custom field. Use after confirming the custom field ID is correct. Deletes the field permanently. |
| `KIT_DELETE_SUBSCRIBER` | Delete Subscriber | Unsubscribe a subscriber from all email communications by their ID. This action permanently unsubscribes a subscriber, removing them from all sequences and forms. The subscriber's historical data is retained but they will no longer receive emails. This operation is idempotent - unsubscribing an already-unsubscribed subscriber succeeds without error. Use KIT_LIST_SUBSCRIBERS to find valid subscriber IDs before calling this action. Returns: Empty response on success (HTTP 204 No Content). Raises: ExecutionFailed: If the subscriber ID doesn't exist (404), authentication fails (401), or other API errors occur. |
| `KIT_DELETE_TAG` | Delete Tag | Tool to delete a tag by ID. Use when you need to remove obsolete or incorrect tags after confirming the tag exists. |
| `KIT_DELETE_WEBHOOK` | Delete Webhook | Tool to delete a webhook by ID. Use when you want to permanently remove a webhook after confirming its ID. |
| `KIT_FILTER_SUBSCRIBERS` | Filter Subscribers | Tool to filter subscribers based on engagement criteria such as email opens, clicks, or delivery status. Use when you need to segment subscribers by their engagement behavior with specific date ranges and count thresholds. |
| `KIT_GET_ACCOUNT` | Get Account | Tool to retrieve current account information. Use after validating API key to fetch account ID, plan type, primary email, and timezone details. |
| `KIT_GET_ACCOUNT_COLORS` | Get Account Colors | Tool to retrieve list of colors associated with the account. Use after confirming authentication to fetch account-specific color palette. |
| `KIT_GET_BROADCAST` | Get Broadcast | Tool to retrieve details of a specific broadcast by ID. Use when you have a valid broadcast ID and need its metadata. |
| `KIT_GET_BROADCAST_CLICKS` | Get Broadcast Clicks | Tool to retrieve link click data for a specific broadcast by ID. Use when you need to analyze which links were clicked and their engagement metrics. |
| `KIT_GET_BROADCAST_STATS` | Get Broadcast Stats | Tool to retrieve statistics for a specific broadcast by ID. Use after a broadcast has been sent to monitor performance. |
| `KIT_GET_CREATOR_PROFILE` | Get Creator Profile | Tool to retrieve the creator profile information for the account. Use when you need creator metadata (name, bio, avatar, profile URL) before publishing or customizing content. |
| `KIT_GET_EMAIL_STATS` | Get Email Stats | Tool to retrieve email statistics for the account. Use after confirming authentication to fetch metrics on emails (sent, opened, clicked) over the last 90 days. |
| `KIT_GET_GROWTH_STATS` | Get Growth Stats | Tool to retrieve growth statistics for the account over a date range. Stats are returned in your sending time zone (not UTC). Defaults to last 90 days if no dates specified. |
| `KIT_GET_SUBSCRIBER` | Get Subscriber | Tool to retrieve a specific subscriber by their ID. Use when you need to fetch detailed information about a single subscriber. |
| `KIT_GET_SUBSCRIBER_STATS` | Get Subscriber Stats | Tool to retrieve email stats for a specific subscriber. Use when you need subscriber engagement metrics (opens, clicks, bounces, rates). Data only available for events from June 2025 onwards. |
| `KIT_LIST_BROADCASTS` | List Broadcasts | Tool to retrieve a paginated list of all broadcasts. Use when you need to enumerate or review broadcast summaries with cursor-based pagination. |
| `KIT_LIST_CUSTOM_FIELDS` | List Custom Fields | Tool to retrieve a paginated list of custom fields. Use after confirming you need to enumerate or inspect all custom fields with cursor-based pagination. |
| `KIT_LIST_EMAIL_TEMPLATES` | List Email Templates | Retrieve a paginated list of all email templates in the Kit account. Returns template details including ID, name, default status, and category. Supports cursor-based pagination for navigating large template collections. Use this when you need to view or iterate through email templates. |
| `KIT_LIST_FORMS` | List Forms | Lists all forms in your Kit account with optional filtering and cursor-based pagination. Use this to retrieve forms when you need to: - Get all available forms (landing pages and embedded forms) - Filter by status (active, archived, trashed) or type (embed, hosted) - Paginate through large collections of forms - Get form IDs and metadata for other operations |
| `KIT_LIST_SEGMENTS` | List Segments | Tool to retrieve a paginated list of segments. Use when you need to enumerate segments with cursor-based pagination for further processing or display. |
| `KIT_LIST_SEQUENCES` | List Sequences | Tool to retrieve a paginated list of all sequences. Use when you need to enumerate sequences with pagination for further processing or display. |
| `KIT_LIST_SUBSCRIBERS` | List Subscribers | Tool to retrieve a list of subscribers. Use when you need to fetch subscriber records with optional filtering, sorting, and pagination. |
| `KIT_LIST_SUBSCRIBERS_FOR_FORM` | List Subscribers For Form | Retrieves subscribers for a specific form by ID with optional filtering and cursor-based pagination. Use this action to: - Get all subscribers who have joined a specific form - Filter subscribers by when they were added to the form (added_after/added_before) - Filter subscribers by when they were created (created_after/created_before) - Filter by subscriber status (e.g., 'active') - Navigate through results using cursor-based pagination (after/before cursors) - Control page size with per_page parameter - Optionally get total subscriber count with include_total_count='true' First use KIT_LIST_FORMS to get valid form_id values. |
| `KIT_LIST_TAGS` | List Tags | Retrieve a paginated list of all tags in the Kit account. Returns tag details including ID, name, and creation date. Supports cursor-based pagination for navigating large tag collections. Use this when you need to view or iterate through tags. |
| `KIT_LIST_TAG_SUBSCRIBERS` | List Tag Subscribers | Tool to retrieve subscribers for a specific tag. Use after confirming the tag ID when you need to list subscribers associated with a tag. |
| `KIT_LIST_WEBHOOKS` | List Webhooks | Retrieve a paginated list of all webhooks configured in the Kit account. Returns webhook details including ID, event type, and target URL. Supports cursor-based pagination for navigating large webhook collections. Use this when you need to view or iterate through webhooks. |
| `KIT_REMOVE_TAG_FROM_SUBSCRIBER` | Remove Tag From Subscriber | Tool to remove a tag from a subscriber using their subscriber ID. Use when you need to untag a subscriber from a specific tag after confirming both tag and subscriber IDs exist. |
| `KIT_TAG_SUBSCRIBER` | Tag Subscriber | Tool to associate a subscriber with a specific tag by ID. Use after confirming tag and subscriber IDs when tagging a subscriber. |
| `KIT_TAG_SUBSCRIBER_BY_EMAIL` | Tag Subscriber by Email | Assigns a tag to an existing subscriber using their email address. The subscriber must already exist in your Kit account. Returns the subscriber's details including the timestamp when they were tagged. Use when you have a valid tag ID and the subscriber's email address. |
| `KIT_UNTAG_SUBSCRIBER_BY_EMAIL` | Untag Subscriber by Email | Tool to remove a tag from a subscriber using their email address. Use when you need to untag an existing subscriber after confirming both the tag ID and subscriber's email address are valid. |
| `KIT_UPDATE_ACCOUNT_COLORS` | Update Account Colors | Tool to update the list of colors for the account. Use when customizing your Kit account's color palette for broadcasts and templates. Maximum 5 hex color codes allowed per account. |
| `KIT_UPDATE_CUSTOM_FIELD` | Update Custom Field | Tool to update a custom field's label. Use after listing or retrieving custom fields and confirming the field ID to rename. |
| `KIT_UPDATE_SUBSCRIBER` | Update Subscriber | Tool to update an existing subscriber's information. Use when you need to modify a subscriber's first name, email address, or custom fields. Supports updating up to 140 custom fields at a time. |
| `KIT_UPDATE_TAG` | Update Tag | Tool to update a tag's name by ID. Use after retrieving tag ID and confirming the new name. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Kit MCP server is an implementation of the Model Context Protocol that connects your AI agent to Kit. It provides structured and secure access so your agent can perform Kit operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Composio API Key and OpenAI API Key
- Primary know-how of OpenAI Agents SDK
- A live Kit project
- Some knowledge of Python or Typescript

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings and copy your API key.

### 2. Install dependencies

Install the Composio SDK and the OpenAI Agents SDK.
```python
pip install composio_openai_agents openai-agents python-dotenv
```

```typescript
npm install @composio/openai-agents @openai/agents dotenv
```

### 3. Set up environment variables

Create a .env file and add your OpenAI and Composio API keys.
```bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com
```

### 4. Import dependencies

What's happening:
- You're importing all necessary libraries.
- The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Kit.
```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
```

### 5. Set up the Composio instance

No description provided.
```python
load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
```

```typescript
dotenv.config();

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
```

### 6. Create a Tool Router session

What is happening:
- You give the Tool Router the user id and the toolkits you want available. Here, it is only kit.
- The router checks the user's Kit connection and prepares the MCP endpoint.
- The returned session.mcp.url is the MCP URL that your agent will use to access Kit.
- This approach keeps things lightweight and lets the agent request Kit tools only when needed during the conversation.
```python
# Create a Kit Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["kit"]
)

mcp_url = session.mcp.url
```

```typescript
// Create Tool Router session for Kit
const session = await composio.create(userId as string, {
  toolkits: ['kit'],
});
const mcpUrl = session.mcp.url;
```

### 7. Configure the agent

No description provided.
```python
# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Kit. "
        "Help users perform Kit operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
```

```typescript
// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Kit. Help users perform Kit operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
```

### 8. Start chat loop and handle conversation

No description provided.
```python
print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

// Simple CLI
const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: 'You: ',
});

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

rl.on('line', async (userInput) => {
  const text = userInput.trim();

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

  if (!text) {
    rl.prompt();
    return;
  }

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

rl.on('close', () => {
  console.log('\n👋 Session ended.');
  process.exit(0);
});
```

## Complete Code

```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["kit"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Kit. "
        "Help users perform Kit operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['kit'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Kit. Help users perform Kit operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

  // Simple CLI
  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: ',
  });

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

  rl.on('line', async (userInput) => {
    const text = userInput.trim();

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

    if (!text) {
      rl.prompt();
      return;
    }

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\n');
    }

    rl.prompt();
  });

  rl.on('close', () => {
    console.log('\nSession ended.');
    process.exit(0);
  });
}

main().catch((err) => {
  console.error('Fatal error:', err);
  process.exit(1);
});
```

## Conclusion

This was a starter code for integrating Kit MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Kit.
Key features:
- Hosted MCP tool integration through Composio's Tool Router
- SQLite session persistence for conversation history
- Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

## How to build Kit MCP Agent with another framework

- [Claude Agent SDK](https://composio.dev/toolkits/kit/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/kit/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/kit/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/kit/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/kit/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/kit/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/kit/framework/cli)
- [Google ADK](https://composio.dev/toolkits/kit/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/kit/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/kit/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/kit/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/kit/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/kit/framework/crew-ai)

## Related Toolkits

- [Reddit](https://composio.dev/toolkits/reddit) - Reddit is a social news platform with thriving user-driven communities (subreddits). It's the go-to place for discussion, content sharing, and viral marketing.
- [Facebook](https://composio.dev/toolkits/facebook) - Facebook is a social media and advertising platform for businesses and creators. It helps you connect, share, and manage content across your public Facebook Pages.
- [Linkedin](https://composio.dev/toolkits/linkedin) - LinkedIn is a professional networking platform for connecting, sharing content, and engaging with business opportunities. It's the go-to place for building your professional brand and unlocking new career connections.
- [Active campaign](https://composio.dev/toolkits/active_campaign) - ActiveCampaign is a marketing automation and CRM platform for managing email campaigns, sales pipelines, and customer segmentation. It helps businesses engage customers and drive growth through smart automation and targeted outreach.
- [ActiveTrail](https://composio.dev/toolkits/active_trail) - ActiveTrail is a user-friendly email marketing and automation platform. It helps you reach subscribers and automate campaigns with ease.
- [Ahrefs](https://composio.dev/toolkits/ahrefs) - Ahrefs is an SEO and marketing platform for site audits, keyword research, and competitor insights. It helps you improve search rankings and drive organic traffic.
- [Amcards](https://composio.dev/toolkits/amcards) - AMCards lets you create and mail personalized greeting cards online. Build stronger customer relationships with easy, automated card campaigns.
- [Beamer](https://composio.dev/toolkits/beamer) - Beamer is a news and changelog platform for in-app announcements and feature updates. It helps companies boost user engagement by sharing news where users are most active.
- [Benchmark email](https://composio.dev/toolkits/benchmark_email) - Benchmark Email is a platform for creating, sending, and tracking email campaigns. It's built to help you engage audiences and analyze results—all in one place.
- [Bigmailer](https://composio.dev/toolkits/bigmailer) - BigMailer is an email marketing platform for managing multiple brands with white-labeling and automation. It helps teams streamline campaigns and simplify integration with Amazon SES.
- [Brandfetch](https://composio.dev/toolkits/brandfetch) - Brandfetch is an API that delivers company logos, colors, and visual branding assets. It helps marketers and developers keep brand visuals consistent everywhere.
- [Brevo](https://composio.dev/toolkits/brevo) - Brevo is an all-in-one email and SMS marketing platform for transactional messaging, automation, and CRM. It helps businesses engage customers and streamline communications through powerful campaign tools.
- [Campayn](https://composio.dev/toolkits/campayn) - Campayn is an email marketing platform for creating, sending, and managing campaigns. It helps businesses engage contacts and grow audiences with easy-to-use tools.
- [Cardly](https://composio.dev/toolkits/cardly) - Cardly is a platform for creating and sending personalized direct mail to customers. It helps businesses break through the digital clutter by getting real engagement via physical mailboxes.
- [ClickSend](https://composio.dev/toolkits/clicksend) - ClickSend is a cloud-based SMS and email marketing platform for businesses. It streamlines communication by enabling quick message delivery and contact management.
- [Crustdata](https://composio.dev/toolkits/crustdata) - CrustData is an AI-powered data intelligence platform for real-time company and people data. It helps B2B sales teams, AI SDRs, and investors react to live business signals.
- [Curated](https://composio.dev/toolkits/curated) - Curated is a platform for collecting, curating, and publishing newsletters. It streamlines content aggregation and distribution for creators and teams.
- [Customerio](https://composio.dev/toolkits/customerio) - Customer.io is a customer engagement platform for targeted messaging across email, SMS, and push. Easily automate, segment, and track communications with your audience.
- [Cutt ly](https://composio.dev/toolkits/cutt_ly) - Cutt.ly is a URL shortening service for managing and analyzing links. Streamline your workflows with quick, trackable, and branded short URLs.
- [Demio](https://composio.dev/toolkits/demio) - Demio is webinar software built for marketers, offering both live and automated sessions with interactive features. It helps teams engage audiences and optimize lead generation through detailed analytics.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Kit MCP?

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.

### Can I use Tool Router MCP with OpenAI Agents SDK?

Yes, you can. OpenAI Agents SDK 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.

### Can I manage the permissions and scopes for Kit while using Tool Router?

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.

### How safe is my data with Composio Tool Router?

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.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)