How to integrate Composio MCP with Claude Agent SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Composio Logo
Claude Agent SDK Logo
divider

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 generate a step-by-step workflow plan, check active connections for all toolkits, download public s3 file to local path, show tool dependencies for workflow setup 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.

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 your Composio account. It provides structured and secure access to your connected tools, so your agent can plan workflows, orchestrate complex actions, manage integrations, and execute cross-tool automations on your behalf.

  • Automated workflow planning and execution: The agent can generate and run step-by-step plans for complex, multi-tool use cases—ensuring tasks are completed reliably, even when they span multiple services.
  • Connection management and discovery: Effortlessly check the status of multiple toolkit connections, discover what integrations are active, and manage how your agent connects to different services.
  • Tool and dependency exploration: Ask your agent to map out tool dependencies, discover related tools, and understand which tools work best together for your workflow.
  • Direct code and command execution: Let the agent run code snippets or shell commands in supported environments, tying together automation across your stack.
  • Bulk and parallel operations: Use specialized tools for parallel execution or to handle many similar tasks at once—speeding up large automations by making multiple calls in a single workflow.

Supported Tools & Triggers

Tools
Ask OracleStatic helper that returns a comprehensive system prompt describing how to plan and execute tasks using the available composio tools and workflows.
Check active connection (deprecated)Deprecated: use check active connections instead for bulk operations.
Check multiple active connectionsCheck active connection status for multiple toolkits or specific connected account ids.
Create PlanThis is a workflow builder that ensures the LLM produces a complete, step-by-step plan for any use case.
Download S3 FileDownload a file from a public s3 (or r2) url to a local path.
Enable triggerEnable a specific trigger for the authenticated user.
Execute agentExecute complex workflows using ai agent reasoning between multiple tool calls.
Execute Composio ToolExecute a tool using the composio api.
Get Tool Dependency GraphGet the dependency graph for a given tool, showing related parent tools that might be useful.
Get required parameters for connectionGets the required parameters for connecting to a toolkit via initiate connection.
Get response schemaRetrieves the response schema for a specified composio tool.
Initiate connectionInitiate a connection to a toolkit with comprehensive authentication support.
List toolkitsList all the available toolkits on composio with filtering options.
List triggersList available triggers and their configuration schemas.
Manage connectionManage a connection to a toolkit with comprehensive authentication support.
Manage connectionsCreate or manage connections to user's apps.
Multi Execute Composio ToolsFast and parallel tool executor for tools discovered through COMPOSIO_SEARCH_TOOLS.
Run bash commandsExecute bash commands in a REMOTE sandbox for file operations, data processing, and system tasks.
Execute Code remotely in work benchProcess REMOTE FILES or script BULK TOOL EXECUTIONS using Python code IN A REMOTE SANDBOX.
Retrieve ToolkitsToolkits are like github, linear, gmail, etc.
Search agentDiscover tools and analyze dependencies for complex workflows using ai agent.
Search Composio ToolsMCP Server Info: COMPOSIO MCP connects 500+ apps—Slack, GitHub, Notion, Google Workspace (Gmail, Sheets, Drive, Calendar), Microsoft (Outlook, Teams), X, Figma, Web Search, Meta apps (WhatsApp, Instagram), TikTok, AI tools like Nano Banana & Veo3, and more—for seamless cross-app automation.
Wait for connectionWait for the user to complete authentication AFTER you have given them an auth URL from COMPOSIO_MANAGE_CONNECTIONS.
Create / Update Recipe from WorkflowConvert the executed workflow into a notebook.
Execute RecipeExecutes a Recipe
Create / Update Skill from WorkflowConvert the executed workflow into a skill using Python Pydantic code.
Get Existing Recipe DetailsGet the details of the existing recipe for a given recipe id.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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

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

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.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

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

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

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

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Composio
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["composio"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
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

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Composio tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="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
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

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

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

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

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Composio
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["composio"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Composio tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

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

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

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.

How to build Composio MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Composio MCP with OpenAI Agents SDK

Google ADK

Google ADK

Use Composio MCP with Google ADK

LangChain

LangChain

Use Composio MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Composio MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Composio MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Composio MCP with LlamaIndex

CrewAI

CrewAI

Use Composio MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Composio MCP?

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.

Can I use Tool Router MCP with Claude Agent SDK?

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.

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

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.

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 Composio data and credentials are handled as safely as possible.

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free