# How to integrate Kaleido MCP with Claude Code ```json { "title": "How to integrate Kaleido MCP with Claude Code", "toolkit": "Kaleido", "toolkit_slug": "kaleido", "framework": "Claude Code", "framework_slug": "claude-code", "url": "https://composio.dev/toolkits/kaleido/framework/claude-code", "markdown_url": "https://composio.dev/toolkits/kaleido/framework/claude-code.md", "updated_at": "2026-05-12T10:16:42.003Z" } ``` ## Introduction Manage your Kaleido directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: - Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach - Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control ## Also integrate Kaleido with - [OpenAI Agents SDK](https://composio.dev/toolkits/kaleido/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/kaleido/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/kaleido/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/kaleido/framework/codex) - [OpenClaw](https://composio.dev/toolkits/kaleido/framework/openclaw) - [Hermes](https://composio.dev/toolkits/kaleido/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/kaleido/framework/cli) - [Google ADK](https://composio.dev/toolkits/kaleido/framework/google-adk) - [LangChain](https://composio.dev/toolkits/kaleido/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/kaleido/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/kaleido/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/kaleido/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/kaleido/framework/crew-ai) ## TL;DR - Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles. - Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling. - Handling Large tool responses out of LLM context to minimize context rot. - Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need. ## Connect Kaleido to Claude Code ### Connecting Kaleido to Claude Code using Composio 1. Add the Composio MCP to Claude ```bash claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp ``` ## What is Claude Code? Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working. Key features include: - Terminal-Native Experience: Work with Claude directly in your command line without switching contexts - MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities - Project Context: Claude understands your project structure and can read, write, and modify files - Interactive Development: Ask questions, debug code, and get help in real-time while coding - Multi-Platform: Works on macOS, Linux, WSL, and Windows ## 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 | Tool slug | Name | Description | |---|---|---| | `KALEIDO_ADD_IDENTITY_PROOF` | Add Organization Identity Proof | Add an x509 identity proof to a Kaleido organization. Use this to register a certificate chain that links an organization's off-chain PKI identity to their blockchain accounts. The certificate will be in 'pending' state until verified. | | `KALEIDO_CREATE_API_KEY` | Create API Key | Creates a new API key for the specified Kaleido organization. The returned apikey secret should be stored securely as it cannot be retrieved again. Use KALEIDO_GET_ORGANIZATIONS to obtain a valid org_id first. Note: Organizations have a limit on active API keys (e.g., 5 for starter plans). | | `KALEIDO_DELETE_API_KEY` | Delete API Key | Permanently deletes an API key by its ID. First use 'Get API Keys' to retrieve the list of API keys and their IDs. The deletion is irreversible. | | `KALEIDO_DELETE_ORGANIZATION_IDENTITY_PROOF` | Delete Organization Identity Proof | Remove an x509 identity proof from a Kaleido organization. This permanently deletes the identity proof. The deletion is irreversible. | | `KALEIDO_GET_API_KEY` | Get API Key | Tool to retrieve details of a specific API key by its ID. Use when you need to get information about a particular API key after obtaining its ID from the Get API Keys action. | | `KALEIDO_GET_API_KEYS` | Get API Keys | Tool to retrieve all API keys associated with the organization. Use when you need an overview of existing API keys after authenticating. | | `KALEIDO_GET_APPLICATION_CREDENTIALS` | Get Application Credentials | Tool to retrieve application credentials for a specific environment. Use when you need to list DApp credentials after environment setup. | | `KALEIDO_GET_BILLING_SUMMARY` | Get Billing Summary | Retrieves a summary of billing data for the specified organization for the current month. Use this to view costs breakdown by memberships, nodes, services, storage, and support. | | `KALEIDO_GET_CONSORTIA` | Get Consortia | Tool to retrieve all consortia associated with the organization. Use after authenticating to view existing consortia. | | `KALEIDO_GET_EVENT_STREAMS` | Get Event Streams | List all event streams configured on a Kaleido blockchain node's Ethconnect REST API Gateway. Event streams provide at-least-once delivery of Ethereum events from your blockchain node to webhook endpoints or WebSocket connections. Use this tool to retrieve the current event stream configurations. Note: Requires environment_id, node_id, and zone_domain to construct the Ethconnect URL, or a full_url override. Without these, falls back to the console API which may not return event streams data. | | `KALEIDO_GET_IDENTITY_PROOF` | Get Organization Identity Proof | Tool to retrieve a specific identity proof for a Kaleido organization. Use when you need details about a specific x509 certificate or identity proof that was previously added to an organization. | | `KALEIDO_GET_INVITATIONS` | Get Invitations | Tool to retrieve all invitations for the current user where they are the target. Use after authenticating to view pending invitations. | | `KALEIDO_GET_MEMBERSHIPS` | Get Memberships | Tool to retrieve all memberships for the current user. Use after authenticating to list user memberships. | | `KALEIDO_GET_ORGANIZATION` | Get Organization | Tool to retrieve details of a specific Kaleido organization by its ID. Use when you need to fetch information about a particular organization. | | `KALEIDO_GET_ORGANIZATION_PLAN` | Get Organization Plan | Retrieve the subscription plan details for a Kaleido organization. Returns plan name, waitlist status, and resource limits including allowed providers, nodes, services, configurations, and features. Use GET_ORGANIZATIONS first to obtain valid org_id values. | | `KALEIDO_GET_ORGANIZATIONS` | Get Organizations | Retrieves all organizations that the authenticated user has access to in Kaleido. Returns organization details including: - Organization ID, name, and type - Subscription plan and billing information - Plan limits (allowed providers, nodes, services, etc.) - Creation and update timestamps Use this action to discover available organizations before performing other organization-specific operations like listing consortia, memberships, or services. | | `KALEIDO_GET_ORG_BILLING_PROVIDER` | Get Organization Billing Provider | Retrieves billing provider information for a specific organization in Kaleido. Returns the type of billing provider (AWS, Stripe, or other) and includes detailed payment information if the organization uses Stripe billing (card details, billing address). | | `KALEIDO_GET_PLANS` | Get Plans | Retrieve all available Kaleido subscription plans. Returns plan details including enabled status, tier level, and resource limits. Use this to discover available plans before creating or upgrading environments. | | `KALEIDO_GET_REGIONS` | Get Regions | Retrieve all available Kaleido deployment regions and their deployment zones. Returns a dictionary of regions (keyed by region code like 'u0', 'e0', 'a0', 'k0', 'u1', 'e1') with each region containing its API console host URL and available deployment zones. Use this action to discover which geographic regions are available for deploying blockchain environments and whether they are currently accepting new deployments. | | `KALEIDO_GET_RELEASES` | Get Releases | Retrieve all available blockchain node software releases from the Kaleido platform. Use this tool to: - List all runtime releases available for different blockchain providers (quorum, geth, besu, corda, fabric) - Check version information and release statuses (ga, beta, interim, deprecated) - Find container image tags associated with each release - Understand upgrade prerequisites via prereq_eips and optional_eips fields Returns a list of releases sorted by creation date, including current and historical versions. No input parameters are required. | | `KALEIDO_GET_ROLE_BY_ID` | Get Role By ID | Retrieve a specific user role assignment within a Kaleido organization. Returns detailed information about the role including user ID, email, role name (e.g., 'admin'), and associated metadata. Use GET_ORGANIZATIONS to obtain org_id and GET_ROLES to obtain role_id values. | | `KALEIDO_GET_ROLES` | Get Roles | Retrieve all user role assignments for a Kaleido organization. Returns each user's role (e.g., 'admin'), email, and associated metadata. Use GET_ORGANIZATIONS first to obtain valid org_id values. | | `KALEIDO_GET_SERVICES` | Get Services | Tool to retrieve all services the current user owns or can see. Use after authenticating to list available services. | | `KALEIDO_GET_TOKEN_FACTORY_TOKENS` | Get Token Factory Tokens | Retrieves all token contracts from a Kaleido Token Factory service. The Token Factory service enables deployment of ERC20 (fungible) and ERC721 (non-fungible) token contracts. This action lists all token contracts created through the service. Prerequisites: - A Token Factory service must be provisioned in your Kaleido environment - Obtain the service URL from GET /services action (look for 'tokenfactory' service type) Returns token contract details including: - Token name, symbol, and type (ERC20/ERC721) - Contract deployment status and address - Minting and burning capabilities - Creation timestamps | | `KALEIDO_GET_WALLET_ACCOUNT_NONCE` | Get Wallet Account Nonce | Retrieve the current nonce (transaction count) of a specific HD wallet account. The nonce is essential for signing Ethereum transactions - it ensures transactions are processed in order and prevents replay attacks. Call this before signing a transaction to get the correct nonce value. Prerequisites: - An HD Wallet service must be provisioned in your Kaleido environment - A wallet must exist (created via POST /wallets) - You need the service API base URL from GET /services endpoint | | `KALEIDO_GET_WALLETS` | Get Wallets | Tool to retrieve HD wallet IDs hosted in the service. Use after creating or importing HD wallets to enumerate available wallets. | | `KALEIDO_UPDATE_ORGANIZATION` | Update Organization | Tool to update a specific organization in Kaleido. Use when you need to modify organization properties such as name, billing details, or authentication settings. First obtain the org_id using the Get Organizations action. | | `KALEIDO_UPDATE_ORG_ROLE` | Update Organization Role | Update the role assignment for a user in a Kaleido organization. Use this to change a user's permissions level (e.g., promoting to admin). Returns the updated role details including the new revision token and updated timestamp. | | `KALEIDO_UPSERT_ORGANIZATION_ROLE` | Upsert Organization Role | Upsert (create or update) a role assignment for a user in a Kaleido organization. Returns 201 for new roles and 200 for updates. The _revision field increments with each update. Use GET_ORGANIZATIONS to obtain valid org_id values. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Kaleido MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Kaleido account. It provides structured and secure access so Claude can perform Kaleido operations on your behalf. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Claude Pro, Max, or API billing enabled Anthropic account - Composio API Key - A Kaleido account - Basic knowledge of Python or TypeScript ### 1. Install Claude Code To install Claude Code, use one of the following methods based on your operating system: ```bash # macOS, Linux, WSL curl -fsSL https://claude.ai/install.sh | bash # Windows PowerShell irm https://claude.ai/install.ps1 | iex # Windows CMD curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd ``` ### 2. Set up Claude Code Open a terminal, go to your project folder, and start Claude Code: - Claude Code will open in your terminal - Follow the prompts to sign in with your Anthropic account - Complete the authentication flow - Once authenticated, you can start using Claude Code ```bash cd your-project-folder claude ``` ### 3. Set up environment variables Create a .env file in your project root with the following variables: - COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code)) - USER_ID identifies the user for session management (use any unique identifier) ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here ``` ### 4. Install Composio library No description provided. ```python pip install composio-core python-dotenv ``` ```typescript npm install @composio/core dotenv ``` ### 5. Generate Composio MCP URL No description provided. ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["kaleido"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http kaleido-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; 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 composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['kaleido'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http kaleido-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ### 6. Run the script and copy the MCP URL No description provided. ```python python generate_mcp_url.py ``` ```typescript node --loader ts-node/esm generate_mcp_url.ts # or if using tsx tsx generate_mcp_url.ts ``` ### 7. Add Kaleido MCP to Claude Code In your terminal, add the MCP server using the command from the previous step. The command format is: - claude mcp add registers a new MCP server with Claude Code - --transport http specifies that this is an HTTP-based MCP server - The server name (kaleido-composio) is how you'll reference it - The URL points to your Composio Tool Router session - --headers includes your Composio API key for authentication After running the command, close the current Claude Code session and start a new one for the changes to take effect. ```bash claude mcp add --transport http kaleido-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY" # Then restart Claude Code exit claude ``` ### 8. Verify the installation Check that your Kaleido MCP server is properly configured. - This command lists all MCP servers registered with Claude Code - You should see your kaleido-composio entry in the list - This confirms that Claude Code can now access Kaleido tools If everything is wired up, you should see your kaleido-composio entry listed: ```bash claude mcp list ``` ### 9. Authenticate Kaleido The first time you try to use Kaleido tools, you'll be prompted to authenticate. - Claude Code will detect that you need to authenticate with Kaleido - It will show you an authentication link - Open the link in your browser (or copy/paste it) - Complete the Kaleido authorization flow - Return to the terminal and start using Kaleido through Claude Code Once authenticated, you can ask Claude Code to perform Kaleido operations in natural language. For example: - "List all API keys for my organization" - "Create a new API key for our consortium" - "Show all event streams configured in this environment" ## Complete Code ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["kaleido"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http kaleido-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; 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 composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['kaleido'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http kaleido-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ## Conclusion You've successfully integrated Kaleido with Claude Code using Composio's MCP server. Now you can interact with Kaleido directly from your terminal using natural language commands. Key features of this setup: - Terminal-native experience without switching contexts - Natural language commands for Kaleido operations - Secure authentication through Composio's managed MCP - Tool Router for dynamic tool discovery and execution Next steps: - Try asking Claude Code to perform various Kaleido operations - Add more toolkits to your Tool Router session for multi-app workflows - Integrate this setup into your development workflow for increased productivity You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities. ## How to build Kaleido MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/kaleido/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/kaleido/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/kaleido/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/kaleido/framework/codex) - [OpenClaw](https://composio.dev/toolkits/kaleido/framework/openclaw) - [Hermes](https://composio.dev/toolkits/kaleido/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/kaleido/framework/cli) - [Google ADK](https://composio.dev/toolkits/kaleido/framework/google-adk) - [LangChain](https://composio.dev/toolkits/kaleido/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/kaleido/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/kaleido/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/kaleido/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/kaleido/framework/crew-ai) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. - [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows. - [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights. - [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews. - [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease. - [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data. ## Frequently Asked Questions ### 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 Claude Code? Yes, you can. Claude Code 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. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)