How to integrate Kaleido MCP with Autogen

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Kaleido Logo
AutoGen Logo
divider

Introduction

This guide walks you through connecting Kaleido to AutoGen using the Composio tool router. By the end, you'll have a working Kaleido agent that can list all api keys for my organization, create a new api key for our consortium, show all event streams configured in this environment, retrieve memberships for the current user through natural language commands.

This guide will help you understand how to give your AutoGen agent real control over a Kaleido account through Composio's Kaleido 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 OpenAI and Composio API keys
  • Install the required dependencies for Autogen and Composio
  • Initialize Composio and create a Tool Router session for Kaleido
  • Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams
  • Configure an Autogen AssistantAgent that can call Kaleido tools
  • Run a live chat loop where you ask the agent to perform Kaleido operations

What is AutoGen?

Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows.

Key features include:

  • Multi-Agent Systems: Build collaborative agent workflows
  • MCP Workbench: Native support for Model Context Protocol tools
  • Streaming HTTP: Connect to external services through streamable HTTP
  • AssistantAgent: Pre-built agent class for tool-using assistants

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

The Kaleido MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Kaleido account. It provides structured and secure access to your blockchain environment, so your agent can perform actions like managing organizations, handling API keys, retrieving memberships, and monitoring event streams on your behalf.

  • Organization and consortium management: Let your agent list, retrieve, and manage organizations and consortia that you have access to—making it easy to keep your blockchain networks organized.
  • API key lifecycle control: Effortlessly create, retrieve, and delete API keys for your organization, so you can handle credential management without manual steps.
  • Membership and access insights: Quickly fetch details about user memberships and organizational access, helping you stay on top of roles and permissions in your blockchain environment.
  • Event stream monitoring: Retrieve and review all event streams configured in your environment, making it simple to keep tabs on real-time blockchain activity.
  • App2App and credential retrieval: Ask your agent to list App2App runtimes and fetch application credentials for specific environments, streamlining application integration and deployment.

Supported Tools & Triggers

Tools
Add Organization Identity ProofTool to add an identity proof to an organization.
Create API KeyTool to create a new API key for an organization.
Delete API KeyTool to delete a specific API key.
Get API KeysTool to retrieve all API keys associated with the organization.
Get App2App RuntimesTool to retrieve App2App runtimes by listing all services and filtering where service == 'app2app'.
Get Application CredentialsTool to retrieve application credentials for a specific environment.
Get ConsortiaTool to retrieve all consortia associated with the organization.
Get Event StreamsTool to list all event streams configured in the environment.
Get MembershipsTool to retrieve all memberships for the current user.
Get OrganizationsTool to retrieve all organizations that the authenticated user has access to.
Get RegionsTool to retrieve the list of deployment zones and endpoints.
Get ReleasesTool to retrieve current and historical versions of node software.
Get RolesTool to retrieve all roles of an organization.
Get ServicesTool to retrieve all services the current user owns or can see.
Get Token Factory TokensTool to retrieve all tokens managed by the Token Factory.
Get Wallet Account NonceTool to retrieve the current nonce of a specific HD wallet account.
Get WalletsTool to retrieve HD wallet IDs hosted in the service.

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

You will need:

  • A Composio API key
  • An OpenAI API key (used by Autogen's OpenAIChatCompletionClient)
  • A Kaleido account you can connect to Composio
  • Some basic familiarity with Autogen and Python async

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.

Install dependencies

bash
pip install composio python-dotenv
pip install autogen-agentchat autogen-ext-openai autogen-ext-tools

Install Composio, Autogen extensions, and dotenv.

What's happening:

  • composio connects your agent to Kaleido via MCP
  • autogen-agentchat provides the AssistantAgent class
  • autogen-ext-openai provides the OpenAI model client
  • autogen-ext-tools provides MCP workbench support

Set up environment variables

bash
COMPOSIO_API_KEY=your-composio-api-key
OPENAI_API_KEY=your-openai-api-key
USER_ID=your-user-identifier@example.com

Create a .env file in your project folder.

What's happening:

  • COMPOSIO_API_KEY is required to talk to Composio
  • OPENAI_API_KEY is used by Autogen's OpenAI client
  • USER_ID is how Composio identifies which user's Kaleido connections to use

Import dependencies and create Tool Router session

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Kaleido session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["kaleido"]
    )
    url = session.mcp.url
What's happening:
  • load_dotenv() reads your .env file
  • Composio(api_key=...) initializes the SDK
  • create(...) creates a Tool Router session that exposes Kaleido tools
  • session.mcp.url is the MCP endpoint that Autogen will connect to

Configure MCP parameters for Autogen

python
# Configure MCP server parameters for Streamable HTTP
server_params = StreamableHttpServerParams(
    url=url,
    timeout=30.0,
    sse_read_timeout=300.0,
    terminate_on_close=True,
    headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
)

Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for.

What's happening:

  • url points to the Tool Router MCP endpoint from Composio
  • timeout is the HTTP timeout for requests
  • sse_read_timeout controls how long to wait when streaming responses
  • terminate_on_close=True cleans up the MCP server process when the workbench is closed

Create the model client and agent

python
# Create model client
model_client = OpenAIChatCompletionClient(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY")
)

# Use McpWorkbench as context manager
async with McpWorkbench(server_params) as workbench:
    # Create Kaleido assistant agent with MCP tools
    agent = AssistantAgent(
        name="kaleido_assistant",
        description="An AI assistant that helps with Kaleido operations.",
        model_client=model_client,
        workbench=workbench,
        model_client_stream=True,
        max_tool_iterations=10
    )

What's happening:

  • OpenAIChatCompletionClient wraps the OpenAI model for Autogen
  • McpWorkbench connects the agent to the MCP tools
  • AssistantAgent is configured with the Kaleido tools from the workbench

Run the interactive chat loop

python
print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Kaleido related question or task to the agent.\n")

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

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

    if not user_input:
        continue

    print("\nAgent is thinking...\n")

    # Run the agent with streaming
    try:
        response_text = ""
        async for message in agent.run_stream(task=user_input):
            if hasattr(message, "content") and message.content:
                response_text = message.content

        # Print the final response
        if response_text:
            print(f"Agent: {response_text}\n")
        else:
            print("Agent: I encountered an issue processing your request.\n")

    except Exception as e:
        print(f"Agent: Sorry, I encountered an error: {str(e)}\n")
What's happening:
  • The script prompts you in a loop with You:
  • Autogen passes your input to the model, which decides which Kaleido tools to call via MCP
  • agent.run_stream(...) yields streaming messages as the agent thinks and calls tools
  • Typing exit, quit, or bye ends the loop

Complete Code

Here's the complete code to get you started with Kaleido and AutoGen:

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Kaleido session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["kaleido"]
    )
    url = session.mcp.url

    # Configure MCP server parameters for Streamable HTTP
    server_params = StreamableHttpServerParams(
        url=url,
        timeout=30.0,
        sse_read_timeout=300.0,
        terminate_on_close=True,
        headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
    )

    # Create model client
    model_client = OpenAIChatCompletionClient(
        model="gpt-5",
        api_key=os.getenv("OPENAI_API_KEY")
    )

    # Use McpWorkbench as context manager
    async with McpWorkbench(server_params) as workbench:
        # Create Kaleido assistant agent with MCP tools
        agent = AssistantAgent(
            name="kaleido_assistant",
            description="An AI assistant that helps with Kaleido operations.",
            model_client=model_client,
            workbench=workbench,
            model_client_stream=True,
            max_tool_iterations=10
        )

        print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
        print("Ask any Kaleido related question or task to the agent.\n")

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

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

            if not user_input:
                continue

            print("\nAgent is thinking...\n")

            # Run the agent with streaming
            try:
                response_text = ""
                async for message in agent.run_stream(task=user_input):
                    if hasattr(message, 'content') and message.content:
                        response_text = message.content

                # Print the final response
                if response_text:
                    print(f"Agent: {response_text}\n")
                else:
                    print("Agent: I encountered an issue processing your request.\n")

            except Exception as e:
                print(f"Agent: Sorry, I encountered an error: {str(e)}\n")

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

Conclusion

You now have an Autogen assistant wired into Kaleido through Composio's Tool Router and MCP. From here you can:
  • Add more toolkits to the toolkits list, for example notion or hubspot
  • Refine the agent description to point it at specific workflows
  • Wrap this script behind a UI, Slack bot, or internal tool
Once the pattern is clear for Kaleido, you can reuse the same structure for other MCP-enabled apps with minimal code changes.

How to build Kaleido MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Kaleido MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Kaleido MCP with Claude Agent SDK

Google ADK

Google ADK

Use Kaleido MCP with Google ADK

LangChain

LangChain

Use Kaleido MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Kaleido MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Kaleido MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Kaleido MCP with LlamaIndex

CrewAI

CrewAI

Use Kaleido MCP with CrewAI

FAQ

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

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

Can I use Tool Router MCP with Autogen?

Yes, you can. Autogen 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 Kaleido tools.

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

Yes, absolutely. You can configure which Kaleido 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 Kaleido 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