SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Composio MCP with Claude Agent SDK

Connect Claude Agent SDK to Composio MCP. Generate a step-by-step workflow plan, check active connections for all toolkits, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Composio logoComposio
No Auth

Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed.

19 Tools

Introduction

This guide walks you through connecting Composio to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Composio agent that can search Composio tools, manage app connections, execute multiple tools at once, enable triggers, and run code in a remote workbench through natural language commands.

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

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

Also integrate Composio with

Claude CodeCursorChatGPTClaude CoworkAntigravityOpenAI Agents SDKGrok BotMuseCodexKimi CodeGrok BuildVS CodeOpenCodeOpenClawHermesAtomic AgentCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

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

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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

The Composio MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to Composio. It provides structured and secure access to Composio tools, service connections, triggers, and remote workspaces, so your agent can discover tools, connect services, execute actions, build plans, and run remote tasks on your behalf.

  • Tool discovery and inspection: Have your agent find relevant tools across Composio's supported apps, inspect their input requirements, and retrieve their response formats.
  • Service connection management: Let the agent check existing connections, start new connections, identify required connection details, and wait for authentication to finish.
  • Single and bulk tool execution: Direct your agent to run one discovered tool or execute several supported tools in parallel for larger tasks.
  • Workflow planning and trigger setup: Instruct your agent to create step-by-step plans, explore related tool dependencies, list available triggers, and enable selected triggers.
  • Remote command and code execution: Have your agent run shell commands in a remote sandbox or use a persistent notebook workspace for file processing and bulk tool operations.

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

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Composio account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • 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

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Composio functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Composio
  const session = await composio.create(USER_ID, {
    toolkits: ['composio'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Composio
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Composio tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Composio
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Composio and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['composio']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Composio tools via Composio.',
    maxTurns: 10,
  };

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Composio through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

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

Check multiple active connections

Check active connection status for multiple toolkits or specific connected account ids.

Create Plan

IMPORTANT - ALWAYS CALL THIS AFTER MANAGE CONNECTIONS TOOL IS EXECUTED.

Enable trigger

Enable a specific trigger for the authenticated user.

Execute Composio Tool

Execute a tool using the composio api.

Get Tool Dependency Graph

Get the dependency graph for a given tool, showing related parent tools that might be useful.

Get required parameters for connection

Gets the required parameters for connecting to a toolkit via initiate connection.

Get response schema

Retrieves the response schema for a specified composio tool.

Initiate connection

Initiate a connection to a toolkit with comprehensive authentication support.

List toolkits

List all the available toolkits on composio with filtering options.

List triggers

List available triggers and their configuration schemas.

Manage connections

Create or manage connections to user's apps.

Multi Execute Composio Tools

Fast and parallel tool executor for tools discovered through COMPOSIO_SEARCH_TOOLS.

Run bash commands

Execute bash commands in a REMOTE sandbox for file operations, data processing, and system tasks.

Execute Code remotely in work bench

Use this persistent Jupyter sandbox only for **remote files** or scripted **bulk tool executions**.

Search Composio Tools

Tool Server Info: Composio connects 500+ apps—Slack, GitHub, Notion, Google Workspace (Gmail, Sheets, Drive, Calendar), Microsoft (Outlook, Teams), X/Twitter, Figma, Web Search / Deep research, Browser tool (scrape URLs, browser automation), Meta apps (Instagram, Meta Ads), TikTok, and more—for seamless cross-app automation.

Wait for connection

Wait for connections to be established for given toolkits.

Check active connection (deprecated)

Deprecated: use check active connections instead for bulk operations.

Wait for connection

Wait for user auth to finish.

Get Tool Schemas

Retrieve input schemas for tools by slug.

FRAMEWORKS

How to build Composio MCP Agent with another framework

Claude Code logo

Claude Code

Use Composio MCP with Claude Code

Cursor logo

Cursor

Use Composio MCP with Cursor

ChatGPT logo

ChatGPT

Use Composio MCP with ChatGPT

Claude Cowork logo

Claude Cowork

Use Composio MCP with Claude Cowork

Antigravity logo

Antigravity

Use Composio MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Composio MCP with OpenAI Agents SDK

Grok Bot logo

Grok Bot

Use Composio MCP with Grok Bot

Muse logo

Muse

Use Composio MCP with Muse

Codex logo

Codex

Use Composio MCP with Codex

Kimi Code logo

Kimi Code

Use Composio MCP with Kimi Code

Grok Build logo

Grok Build

Use Composio MCP with Grok Build

VS Code logo

VS Code

Use Composio MCP with VS Code

OpenCode logo

OpenCode

Use Composio MCP with OpenCode

OpenClaw logo

OpenClaw

Use Composio MCP with OpenClaw

Hermes logo

Hermes

Use Composio MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Composio MCP with Atomic Agent

CLI logo

CLI

Use Composio MCP with CLI

Google ADK logo

Google ADK

Use Composio MCP with Google ADK

LangChain logo

LangChain

Use Composio MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Composio MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Composio MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Composio MCP with LlamaIndex

CrewAI logo

CrewAI

Use Composio MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Composio MCP with Pydantic AI

AutoGen logo

AutoGen

Use Composio MCP with AutoGen

FAQ

Frequently asked questions

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

Yes, you can. Claude Agent 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 Composio tools.

Yes, absolutely. You can configure which Composio 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 Composio data and credentials are handled as safely as possible.

Start with Composio.It takes 30 seconds.

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

Start building