How to integrate Kaleido MCP with LangChain

This guide walks you through connecting Kaleido to LangChain using the Composio tool router. By the end, you'll have a working Kaleido agent that can list all api keys for your organization, create a new api key for our consortium, show all event streams configured in this environment through natural language commands. This guide will help you understand how to give your LangChain 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.

Get started for freeGet a demo
Kaleido logoKaleido
Api Key

Kaleido is a full-stack platform for building and managing enterprise blockchain networks and applications. It streamlines secure deployment, governance, and scaling for blockchain solutions.

29 Tools

Introduction

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

This guide will help you understand how to give your LangChain 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.

Also integrate Kaleido with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Kaleido project to Composio
  • Create a Tool Router MCP session for Kaleido
  • Initialize an MCP client and retrieve Kaleido tools
  • Build a LangChain agent that can interact with Kaleido
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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.

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

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

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

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Kaleido functionality through MCP
6

Initialize Composio client

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

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Kaleido tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['kaleido']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Kaleido tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Kaleido tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "kaleido-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Kaleido MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Kaleido tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

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

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

rl.prompt();

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

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

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

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

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

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

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

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['kaleido']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "kaleido-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Kaleido related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\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

You've successfully built a LangChain agent that can interact with Kaleido through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

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

Add Organization Identity Proof

Add an x509 identity proof to a Kaleido organization.

Create API Key

Creates a new API key for the specified Kaleido organization.

Delete API Key

Permanently deletes an API key by its ID.

Delete Organization Identity Proof

Remove an x509 identity proof from a Kaleido organization.

Get API Key

Tool to retrieve details of a specific API key by its ID.

Get API Keys

Tool to retrieve all API keys associated with the organization.

Get Application Credentials

Tool to retrieve application credentials for a specific environment.

Get Billing Summary

Retrieves a summary of billing data for the specified organization for the current month.

Get Consortia

Tool to retrieve all consortia associated with the organization.

Get Event Streams

List all event streams configured on a Kaleido blockchain node's Ethconnect REST API Gateway.

Get Organization Identity Proof

Tool to retrieve a specific identity proof for a Kaleido organization.

Get Invitations

Tool to retrieve all invitations for the current user where they are the target.

Get Memberships

Tool to retrieve all memberships for the current user.

Get Organization

Tool to retrieve details of a specific Kaleido organization by its ID.

Get Organization Plan

Retrieve the subscription plan details for a Kaleido organization.

Get Organizations

Retrieves all organizations that the authenticated user has access to in Kaleido.

Get Organization Billing Provider

Retrieves billing provider information for a specific organization in Kaleido.

Get Plans

Retrieve all available Kaleido subscription plans.

Get Regions

Retrieve all available Kaleido deployment regions and their deployment zones.

Get Releases

Retrieve all available blockchain node software releases from the Kaleido platform.

Get Role By ID

Retrieve a specific user role assignment within a Kaleido organization.

Get Roles

Retrieve all user role assignments for a Kaleido organization.

Get Services

Tool to retrieve all services the current user owns or can see.

Get Token Factory Tokens

Retrieves all token contracts from a Kaleido Token Factory service.

Get Wallet Account Nonce

Retrieve the current nonce (transaction count) of a specific HD wallet account.

Get Wallets

Tool to retrieve HD wallet IDs hosted in the service.

Update Organization

Tool to update a specific organization in Kaleido.

Update Organization Role

Update the role assignment for a user in a Kaleido organization.

Upsert Organization Role

Upsert (create or update) a role assignment for a user in a Kaleido organization.

FRAMEWORKS

How to build Kaleido MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Kaleido MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Kaleido MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Kaleido MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Kaleido MCP with Claude Cowork

Codex logo

Codex

Use Kaleido MCP with Codex

OpenClaw logo

OpenClaw

Use Kaleido MCP with OpenClaw

Hermes logo

Hermes

Use Kaleido MCP with Hermes

CLI logo

CLI

Use Kaleido MCP with CLI

Google ADK logo

Google ADK

Use Kaleido MCP with Google ADK

Vercel AI SDK logo

Vercel AI SDK

Use Kaleido MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Kaleido MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Kaleido MCP with LlamaIndex

CrewAI logo

CrewAI

Use Kaleido MCP with CrewAI

FAQ

Frequently asked questions

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.

Yes, you can. LangChain 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.

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.

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.

Start with Kaleido.It takes 30 seconds.

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

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies