How to integrate Agenty MCP with Claude Agent SDK

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

Introduction

This guide walks you through connecting Agenty to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Agenty agent that can clone my top-performing agent for news sites, list all my running web scraping agents, create a new agent to monitor product prices, delete an outdated agent by its id through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Agenty account through Composio's Agenty 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 Agenty
  • Configure an AI agent that can use Agenty as a tool
  • Run a live chat session where you can ask the agent to perform Agenty 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 Agenty MCP server, and what's possible with it?

The Agenty MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Agenty account. It provides structured and secure access to your web scraping agents and automation tools, so your agent can perform actions like creating, managing, cloning, and monitoring scraping agents, as well as handling API keys and templates—all on your behalf.

  • Agent creation and configuration: Instantly create new scraping or automation agents, set up their configurations, and optionally auto-start them—all without manual coding.
  • Clone and update agents: Duplicate existing agents to streamline workflows or update agent settings to refine your data extraction processes.
  • Fetch and manage agents: List all active agents in your account, retrieve details for any agent, and organize your entire automation fleet from a single place.
  • Template selection and management: Browse public agent templates or sample agents, making it easy to kickstart new projects or standardize scraping tasks.
  • API key management: Create, download, or delete API keys for secure programmatic access and efficient credential management, keeping your automation environment safe and organized.

Supported Tools & Triggers

Tools
Clone Agent by IDTool to clone an existing agent by its id.
Create AgentTool to create a new agent.
Get Agent TemplatesTool to fetch all public agent templates and sample agents.
Delete Agent by IDTool to delete a single agent by its id.
Fetch all agentsTool to fetch all active agents under an account.
Get Agent by IDTool to fetch details of a specific agent by its id.
Update Agent by IDTool to update an agent's configuration and settings by agent id.
Create API KeyTool to create a new api key.
Delete API key by IDTool to delete an api key by its key id.
Download API keysTool to download all api keys under an account in csv format.
Get all API keysTool to retrieve all api keys under an account.
Get API key by IDTool to get an api key by key id.
Reset API key by IDTool to reset an api key by key id.
Update API key by IDTool to update an api key by its id.
Change API key status by IDTool to enable or disable an api key by its id.
Get all connectionsTool to get all connections.
Create API KeyTool to create a new api key.
Get dashboard reports and usageTool to fetch account reports like pages used by agent, date, and product.
Get agent input by IDTool to get agent input by agent id.
Update Input by Agent IDTool to update agent input by agent id.
Download jobsTool to download all jobs in csv format.
Download job file by IDTool to download output files by job id.
Download Job Result by IDTool to download the agent output result by job id.
Fetch all jobsTool to fetch all jobs under an account.
Get Job by IDTool to fetch details of a specific job by its id.
Get Job Logs by IDTool to fetch logs for a given job by its id.
List job files by IDTool to list output files by job id.
Start Agent JobTool to start a new agent job.
Stop Job by IDTool to stop a running job by job id.
Clear List RowsTool to clear all rows in a list by its id.
Create ListTool to create a new list.
Delete List by IDTool to delete a specific list by its id.
Download listsTool to download all lists in csv format.
Get all listsTool to retrieve all lists under an account.
Fetch List Rows by IDTool to fetch all rows in a specified list.
Update List by IDTool to update a list's name or description by list id.
Upload CSV file to ListTool to upload a csv file to a list.
Add Agents to ProjectTool to add agent(s) to a project.
Create ProjectTool to create a new project.
Get all projectsTool to retrieve all projects under an account.

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 Agenty 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 Agenty 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 Agenty
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["agenty"]
    )

    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 Agenty
  • 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 Agenty 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 Agenty
  • 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 Agenty 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 Agenty
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["agenty"]
    )

    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 Agenty 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 Agenty 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 Agenty MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Agenty MCP with OpenAI Agents SDK

Google ADK

Google ADK

Use Agenty MCP with Google ADK

LangChain

LangChain

Use Agenty MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Agenty MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Agenty MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Agenty MCP with LlamaIndex

CrewAI

CrewAI

Use Agenty MCP with CrewAI

FAQ

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

With a standalone Agenty MCP server, the agents and LLMs can only access a fixed set of Agenty tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Agenty 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 Agenty tools.

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

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

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
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