execute-tool-planningLABSCO SUMMARY
One key instead of six provider accounts.
The work it removes is integration: a question about a wallet's history and the sentiment around a token would otherwise mean separate accounts, separate keys and separate billing at each provider. Planning being deterministic matters more than it sounds — it means the same question is answered by the same sources twice running.
What it is
A routing layer in front of paid data providers. In its default mode a request is planned and executed in one call; planning is deterministic, so the same question composes the same set of provider calls.
What you get
- One endpoint and one key covering every provider behind the gateway
- Several provider APIs composed inside a single request
- Deterministic planning — semantically identical prompts produce the same composition
- A separate planning step, when you switch it on, so the plan can be seen before it runs
- The crypto vertical at launch: market intelligence, wallet transactions and relations, whale movement and sentiment, from providers including Dune, DefiLlama, Zerion, Xverse, Coingecko and Cielo
Requirements
A Kirha access code — the beta is invite-based, and you request one from the Kirha app. The separate planning mode is off unless you turn it on with an environment switch.
Setup effort
One command plus a key — npx @kirha/mcp-installer install --client <YOUR_CLIENT> --key <YOUR_API_KEY>, then supply credentials
USE CASES
01
Asking one question that needs several data sources
State the question and let the gateway work out which providers answer it and combine what comes back, instead of calling each and stitching results yourself.
02
Seeing what it will call before it calls it
Turn on the separate planning step and read the composition first — worth doing while you are learning what the gateway reaches for.
03
Researching a wallet or a token
Transactions, relations, whale movement and sentiment come from different providers; one request pulls them together into a single answer.
04
Getting the same answer twice
Planning is deterministic, so a repeated question composes the same provider calls — which is what makes an answer worth citing in a report.
2 tools
Listed in project docs. Your client may show a different list.
create-tool-planningBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- npx on PATH
- A Kirha API key, passed to the installer as --key <api-key> — the beta is invite-based; request an access code at https://app.kirha.ai/auth/claim-invite-code
INSTALLATION
Connect your client
The command adds the entry to your client for you; any other client needs an entry you write yourself.
Server setup
TERMINAL
npx @kirha/mcp-installer install --client <YOUR_CLIENT> --key <YOUR_API_KEY><YOUR_CLIENT> is your client as the Kirha MCP Installer names it — the supported clients are listed at https://github.com/kirha-ai/mcp-installer#supported-clients —, and <YOUR_API_KEY> is your Kirha API key.
