# How to integrate Kaleido MCP with Mastra AI ```json { "title": "How to integrate Kaleido MCP with Mastra AI", "toolkit": "Kaleido", "toolkit_slug": "kaleido", "framework": "Mastra AI", "framework_slug": "mastra-ai", "url": "https://composio.dev/toolkits/kaleido/framework/mastra-ai", "markdown_url": "https://composio.dev/toolkits/kaleido/framework/mastra-ai.md", "updated_at": "2026-05-12T10:16:42.003Z" } ``` ## Introduction This guide walks you through connecting Kaleido to Mastra AI 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 Mastra AI 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 SDK](https://composio.dev/toolkits/kaleido/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/kaleido/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/kaleido/framework/claude-code) - [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) - [LlamaIndex](https://composio.dev/toolkits/kaleido/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/kaleido/framework/crew-ai) ## TL;DR Here's what you'll learn: - Set up your environment so Mastra, OpenAI, and Composio work together - Create a Tool Router session in Composio that exposes Kaleido tools - Connect Mastra's MCP client to the Composio generated MCP URL - Fetch Kaleido tool definitions and attach them as a toolset - Build a Mastra agent that can reason, call tools, and return structured results - Run an interactive CLI where you can chat with your Kaleido agent ## What is Mastra AI? Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP. Key features include: - MCP Client: Built-in support for Model Context Protocol servers - Toolsets: Organize tools into logical groups - Step Callbacks: Monitor and debug agent execution - OpenAI Integration: Works with OpenAI models via @ai-sdk/openai ## 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 your AI agent to Kaleido. It provides structured and secure access so your agent can perform Kaleido operations on your behalf through a secure, permission-based interface. 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: - Node.js 18 or higher - A Composio account with an active API key - An OpenAI API key - Basic familiarity with TypeScript ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. - You need credits or a connected billing setup to use the models. - Store the key somewhere safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Go to Settings and copy your API key. - This key lets your Mastra agent talk to Composio and reach Kaleido through MCP. ### 2. Install dependencies Install the required packages. What's happening: - @composio/core is the Composio SDK for creating MCP sessions - @mastra/core provides the Agent class - @mastra/mcp is Mastra's MCP client - @ai-sdk/openai is the model wrapper for OpenAI - dotenv loads environment variables from .env ```bash npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates your requests to Composio - COMPOSIO_USER_ID tells Composio which user this session belongs to - OPENAI_API_KEY lets the Mastra agent call OpenAI models ```bash COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key_here ``` ### 4. Import libraries and validate environment What's happening: - dotenv/config auto loads your .env so process.env.* is available - openai gives you a Mastra compatible model wrapper - Agent is the Mastra agent that will call tools and produce answers - MCPClient connects Mastra to your Composio MCP server - Composio is used to create a Tool Router session ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Agent } from "@mastra/core/agent"; import { MCPClient } from "@mastra/mcp"; import { Composio } from "@composio/core"; import * as readline from "readline"; import type { AiMessageType } from "@mastra/core/agent"; const openaiAPIKey = process.env.OPENAI_API_KEY; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey as string, }); ``` ### 5. Create a Tool Router session for Kaleido What's happening: - create spins up a short-lived MCP HTTP endpoint for this user - The toolkits array contains "kaleido" for Kaleido access - session.mcp.url is the MCP URL that Mastra's MCPClient will connect to ```typescript async function main() { const session = await composio.create( composioUserID as string, { toolkits: ["kaleido"], }, ); const composioMCPUrl = session.mcp.url; console.log("Kaleido MCP URL:", composioMCPUrl); ``` ### 6. Configure Mastra MCP client and fetch tools What's happening: - MCPClient takes an id for this client and a list of MCP servers - The headers property includes the x-api-key for authentication - getTools fetches the tool definitions exposed by the Kaleido toolkit ```typescript const mcpClient = new MCPClient({ id: composioUserID as string, servers: { nasdaq: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); console.log("Fetching MCP tools from Composio..."); const composioTools = await mcpClient.getTools(); console.log("Number of tools:", Object.keys(composioTools).length); ``` ### 7. Create the Mastra agent What's happening: - Agent is the core Mastra agent - name is just an identifier for logging and debugging - instructions guide the agent to use tools instead of only answering in natural language - model uses openai("gpt-5") to configure the underlying LLM ```typescript const agent = new Agent({ name: "kaleido-mastra-agent", instructions: "You are an AI agent with Kaleido tools via Composio.", model: "openai/gpt-5", }); ``` ### 8. Set up interactive chat interface What's happening: - messages keeps the full conversation history in Mastra's expected format - agent.generate runs the agent with conversation history and Kaleido toolsets - maxSteps limits how many tool calls the agent can take in a single run - onStepFinish is a hook that prints intermediate steps for debugging ```typescript let messages: AiMessageType[] = []; console.log("Chat started! Type 'exit' or 'quit' to end.\n"); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); 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; } messages.push({ id: crypto.randomUUID(), role: "user", content: trimmedInput, }); console.log("\nAgent is thinking...\n"); try { const response = await agent.generate(messages, { toolsets: { kaleido: composioTools, }, maxSteps: 8, }); const { text } = response; if (text && text.trim().length > 0) { console.log(`Agent: ${text}\n`); messages.push({ id: crypto.randomUUID(), role: "assistant", content: text, }); } } catch (error) { console.error("\nError:", error); } rl.prompt(); }); rl.on("close", async () => { console.log("\nSession ended."); await mcpClient.disconnect(); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Complete Code ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Agent } from "@mastra/core/agent"; import { MCPClient } from "@mastra/mcp"; import { Composio } from "@composio/core"; import * as readline from "readline"; import type { AiMessageType } from "@mastra/core/agent"; const openaiAPIKey = process.env.OPENAI_API_KEY; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey as string }); async function main() { const session = await composio.create(composioUserID as string, { toolkits: ["kaleido"], }); const composioMCPUrl = session.mcp.url; const mcpClient = new MCPClient({ id: composioUserID as string, servers: { kaleido: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); const composioTools = await mcpClient.getTools(); const agent = new Agent({ name: "kaleido-mastra-agent", instructions: "You are an AI agent with Kaleido tools via Composio.", model: "openai/gpt-5", }); let messages: AiMessageType[] = []; const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (input: string) => { const trimmed = input.trim(); if (["exit", "quit"].includes(trimmed.toLowerCase())) { rl.close(); return; } messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed }); const { text } = await agent.generate(messages, { toolsets: { kaleido: composioTools }, maxSteps: 8, }); if (text) { console.log(`Agent: ${text}\n`); messages.push({ id: crypto.randomUUID(), role: "assistant", content: text }); } rl.prompt(); }); rl.on("close", async () => { await mcpClient.disconnect(); process.exit(0); }); } main(); ``` ## Conclusion You've built a Mastra AI agent that can interact with Kaleido through Composio's Tool Router. You can extend this further by: - Adding other toolkits like Gmail, Slack, or GitHub - Building a web-based chat interface around this agent - Using multiple MCP endpoints to enable cross-app workflows ## 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 Code](https://composio.dev/toolkits/kaleido/framework/claude-code) - [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) - [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 Mastra AI? Yes, you can. Mastra AI 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)