Kaleido
Kaleido is a full-stack platform for building and managing enterprise blockchain networks and applications.
Verdict
Common use cases
- Audit API keys across all environments
- Register x.509 certificates for new orgs
- List event streams before a deploy
- Retrieve DApp credentials during incident response
- Enumerate App2App runtimes for capacity planning
Integration
- Vendor
- Kaleido
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 17
- Composio slug
kaleido
Tools
- Add Organization Identity Proof
Tool to add an identity proof to an organization. Use when registering an x.509 certificate chain for an org immediately after creation.
- Create API Key
Tool to create a new API key for an organization. Use after confirming the org_id.
- Delete API Keydestructive
Tool to delete a specific API key. Use when you need to remove an API key by its identifier after confirming it's no longer in use.
- 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.
- Get App2App Runtimes
Tool to retrieve App2App runtimes by listing all services and filtering where service == 'app2app'. Use after authenticating to enumerate App2App service instances.
- Get Application Credentials
Tool to retrieve application credentials for a specific environment. Use when you need to list DApp credentials after environment setup.
- Get Consortia
Tool to retrieve all consortia associated with the organization. Use after authenticating to view existing consortia.
- Get Event Streams
Tool to list all event streams configured in the environment. Use when you need to retrieve current event stream setups.
- Get Memberships
Tool to retrieve all memberships for the current user. Use after authenticating to list user memberships.
- Get Organizations
Tool to retrieve all organizations that the authenticated user has access to. Use after authenticating to list available organizations.
- Get Regions
Tool to retrieve the list of deployment zones and endpoints. Use after authenticating to list available regions.
- Get Releases
Tool to retrieve current and historical versions of node software. Use when you need to list all runtime releases available in the Kaleido platform.
- Get Roles
Tool to retrieve all roles of an organization. Use when you need to audit or manage user roles after confirming a valid organization ID.
- Get Services
Tool to retrieve all services the current user owns or can see. Use after authenticating to list available services.
- Get Token Factory Tokens
Tool to retrieve all tokens managed by the Token Factory. Use after authenticating to list available tokens.
- Get Wallet Account Nonce
Tool to retrieve the current nonce of a specific HD wallet account. Use before signing a transaction to determine the next transaction count.
- Get Wallets
Tool to retrieve HD wallet IDs hosted in the service. Use after creating or importing HD wallets to enumerate available wallets.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Developer Tools. 2. Find Kaleido in the list and click Connect. 3. Log into your Kaleido account in a separate tab, go to Account Settings > API Keys, and generate a new key with read and write permissions for the consortia and environments you want to manage. 4. Copy the key and paste it into the Switchy prompt when asked. 5. Click Authorize to complete the connection. 6. Test it by opening any Space, typing '@Kaleido get consortia', and sending the message. 7. You should see a list of your consortia appear in the response. 8. If the list is empty or you see an error, double-check the API key has the correct scopes and hasn't expired. 9. Once confirmed, you can invoke any of the 17 tools by @mentioning Kaleido and describing the task in plain language.
What teammates see: by default, memories from Kaleido are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Consortia
@Kaleido get consortia. Show the name, ID, and creation date for each one.Open in a Space →
Create New API Key
@Kaleido create a new API key for org_id abc123. Label it 'CI Pipeline Key' and set expiration to 90 days.Open in a Space →
Audit Existing Keys
@Kaleido get all API keys for my organization. Include the key ID, label, and last-used timestamp.Open in a Space →
Register Identity Proof
@Kaleido add an identity proof to org_id xyz789. Use the certificate chain from our PKI root CA.Open in a Space →
List Event Streams
@Kaleido list event streams in environment env_456. Include the stream name, status, and target webhook URL.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@kaleido list all consortia in my organization and show me which environments are currently active
Found 2 consortia in your organization: 1. **supply-chain-prod** (ID: czr8x3m9f) - Environment: production-mainnet (active) - Environment: staging-testnet (active) - Nodes: 4 active 2. **partner-integration-dev** (ID: czr8x3m9g) - Environment: dev-sandbox (active) - Nodes: 2 active All environments are currently running. The production consortium has 4 validator nodes distributed across your partner organizations.
This example demonstrates Kaleido's consortium management capabilities. Requires an API key with read access to consortia resources. Useful for getting a high-level view of your blockchain network topology before drilling into specific environments or node configurations.
@kaleido create a new API key named 'ci-pipeline-key' for automated deployments and show me the credentials
Created new API key successfully: **Name:** ci-pipeline-key **Key ID:** ak_7h2m9x4p **Secret:** kld_sec_8x9m2n4p7q... (full secret shown once) **Created:** 2024-01-15 14:32 UTC **Permissions:** Full organization access ⚠️ **Important:** Store this secret securely — it won't be displayed again. The key is now active and can authenticate API requests immediately. Consider restricting permissions to specific consortia if this key is only for deployment automation.
This write operation creates a live API key with immediate effect. The secret is only shown once at creation time, so users must capture it securely. Best practice: scope keys to minimum required permissions rather than org-wide access, though this example shows the default behavior.
@kaleido review all event streams in the production-mainnet environment and summarize which smart contract events we're currently monitoring
Analyzed 3 event streams in **production-mainnet**: **Stream 1: order-events** (ID: es_4m7x2n) - Monitoring: OrderCreated, OrderFulfilled, OrderCancelled - Contract: SupplyChainManager (0x742d...) - Webhook: https://api.yourapp.com/webhooks/orders - Status: Active, 1,247 events processed today **Stream 2: payment-tracking** (ID: es_9p3x7k) - Monitoring: PaymentReceived, PaymentRefunded - Contract: PaymentProcessor (0x8a3f...) - Webhook: https://api.yourapp.com/webhooks/payments - Status: Active, 89 events today **Stream 3: audit-log** (ID: es_2k8m4n) - Monitoring: All events (wildcard) - Contract: AuditTrail (0x1c5e...) - Webhook: https://archive.yourapp.com/audit - Status: Active, 3,402 events today You're capturing order lifecycle events, payment transactions, and a complete audit trail. All streams are delivering successfully with no backlog.
This synthesis example combines Kaleido's event stream listing with AI reasoning to provide business context. Event streams are read-only queries here, but they represent active webhooks that push blockchain events to external systems. Useful for auditing what data is flowing out of your blockchain network.
Use-case deep-dives
When Kaleido wins for managing blockchain app credentials at scale
A 6-person fintech team runs three Ethereum-based applications across dev, staging, and production environments on Kaleido's managed blockchain platform. They rotate API keys monthly and need to audit which credentials are active across consortia. The Get Application Credentials and Get API Keys tools let them script the audit in a shared Switchy workspace, pulling current keys for each environment without logging into the Kaleido console. The Create API Key and Delete API Key tools handle rotation in the same session. This works cleanly if your team already runs on Kaleido's infrastructure. If you're evaluating blockchain platforms or use a different provider, this MCP won't help—it's tightly coupled to Kaleido's API surface. For teams committed to Kaleido, this MCP turns credential hygiene into a 10-minute weekly task instead of a half-day manual slog.
When this MCP speeds up blockchain event troubleshooting
A 3-person backend team supports a supply-chain DApp that listens to on-chain events via Kaleido's event streams. When a customer reports missing webhook deliveries, the on-call engineer needs to verify stream configuration and check if the App2App runtime is healthy. The Get Event Streams and Get App2App Runtimes tools surface this data in Switchy without context-switching to the Kaleido dashboard. The engineer confirms the stream is active, sees the runtime status, and escalates to Kaleido support with the exact service IDs in under five minutes. This scenario assumes you're using Kaleido's event streaming feature—if you poll contract state directly or use a different event indexer, the MCP adds no value. For teams relying on Kaleido's managed event infrastructure, this MCP cuts incident triage time in half.
When Kaleido MCP simplifies multi-org blockchain setup
A 5-person enterprise blockchain team onboards new partners to a permissioned Ethereum consortium every quarter. Each partner needs an organization identity registered with an x.509 certificate chain, then API keys provisioned for their integration team. The Add Organization Identity Proof and Create API Key tools let the onboarding lead script the entire flow in Switchy, reducing manual steps from 12 to 3. The Get Consortia tool confirms the partner's org appears in the consortium roster before handing off credentials. This works if you manage multiple organizations on Kaleido and onboard partners regularly. If you run a single-org setup or onboard fewer than twice a year, the manual console workflow is faster. For teams onboarding at scale, this MCP turns a 90-minute checklist into a 15-minute scripted task.
Frequently asked
What does the Kaleido MCP do in Switchy?
The Kaleido MCP lets your team manage blockchain infrastructure directly from Switchy. You can create and delete API keys, retrieve consortia and environments, configure event streams, and manage App2App runtimes without switching to the Kaleido console. It's built for teams running enterprise blockchain nodes who want to script infrastructure tasks alongside their other workflows.
Do I need admin access to connect Kaleido MCP?
Yes. The MCP uses an API key that requires organization-level permissions in Kaleido. You'll need the ability to create and manage API keys, view consortia, and access environment credentials. If you're only a member of a specific environment, you won't have sufficient scope to authenticate the integration.
Can the Kaleido MCP deploy smart contracts or send transactions?
No. The MCP focuses on infrastructure management — API keys, identity proofs, event streams, and runtime configuration. It doesn't interact with the blockchain itself. For contract deployment or transaction signing, use Kaleido's application credentials with a web3 library or the Kaleido REST API directly.
How is this different from using the Kaleido console or API directly?
The MCP surfaces Kaleido's infrastructure controls inside Switchy's shared workspace, so your team can automate setup tasks without context-switching. You lose the console's visual network topology and detailed logs, but gain the ability to chain Kaleido operations with other MCPs — like creating a node, then posting the endpoint to Slack.
Who on the team should connect the Kaleido MCP?
Whoever holds your organization's Kaleido API key with full permissions. Typically that's a DevOps lead or infrastructure engineer. Once connected, any Switchy team member can invoke the tools, so limit access to people who understand the cost and security implications of spinning up blockchain nodes.