KIRHA MCP
KIRHA runs a remote MCP server at https://mcp.kirha.com/mcp (https://mcp.kirha.com works too). Any client that supports the Model Context Protocol over Streamable HTTP can connect to it directly, with no local process.
Send your API key in the Authorization header, with or without the Bearer prefix. Listing the tools works without a key, searching needs one.
Option 1: MCP Installer CLI (recommended)
The fastest way to get started. The @kirha/mcp-installer package writes the config for your client. If you use the KIRHA CLI, kirha mcp install does the same and reuses the key from kirha auth login.
kirha-ai/mcp-installer
npx @kirha/mcp-installer install --client claudecode --key KIRHA_API_KEYnpx @kirha/mcp-installer install --client opencode --key KIRHA_API_KEYnpx @kirha/mcp-installer install --client codex --key KIRHA_API_KEYnpx @kirha/mcp-installer install --client droid --key KIRHA_API_KEYnpx @kirha/mcp-installer install --client gemini --key KIRHA_API_KEYExperimental
Gemini CLI support is experimental due to server compatibility with Streamable HTTP transport.
Update or remove
# Update your API key
npx @kirha/mcp-installer update --client claudecode --key KIRHA_API_KEY
# Remove KIRHA from your client
npx @kirha/mcp-installer remove --client claudecode# Update your API key
npx @kirha/mcp-installer update --client opencode --key KIRHA_API_KEY
# Remove KIRHA from your client
npx @kirha/mcp-installer remove --client opencode# Update your API key
npx @kirha/mcp-installer update --client codex --key KIRHA_API_KEY
# Remove KIRHA from your client
npx @kirha/mcp-installer remove --client codex# Update your API key
npx @kirha/mcp-installer update --client droid --key KIRHA_API_KEY
# Remove KIRHA from your client
npx @kirha/mcp-installer remove --client droid# Update your API key
npx @kirha/mcp-installer update --client gemini --key KIRHA_API_KEY
# Remove KIRHA from your client
npx @kirha/mcp-installer remove --client geminiOption 2: Manual config
Add the KIRHA MCP server to your client configuration yourself.
Create an account at app.kirha.com.
Create an API key at app.kirha.com/api-keys.
Add the server to your MCP client:
claude mcp add --transport http kirha https://mcp.kirha.com/mcp \
--header "Authorization: Bearer KIRHA_API_KEY"Or add it to your .mcp.json:
{
"mcpServers": {
"kirha": {
"type": "http",
"url": "https://mcp.kirha.com/mcp",
"headers": {
"Authorization": "Bearer KIRHA_API_KEY"
}
}
}
}Add to ~/.config/opencode/opencode.json:
{
"mcp": {
"kirha": {
"type": "remote",
"url": "https://mcp.kirha.com/mcp",
"enabled": true,
"headers": {
"Authorization": "Bearer KIRHA_API_KEY"
}
}
}
}Done. Your agent can now search across every vertical on KIRHA.
Exposed tool
The server exposes one read-only tool, Search (readOnlyHint: true).
| Input | Required | Description |
|---|---|---|
query | Yes | The question to answer. Be specific: name the asset, company, place or period it is about. |
focus | No | Vertical slug that restricts the search to one vertical. Leave it out to search every vertical. Slugs are listed on the Verticals page. |
KIRHA plans the query, calls the right providers and returns each provider's raw result, so the agent can cite its sources. When no specialized provider fits, the search falls back to web search. Each search spends credits from the organization that owns the API key.
The server also sends instructions to the client on connect, telling the agent to call Search whenever an answer depends on facts that change over time or must be traceable to a source.
KIRHA returns structured data straight from the providers. Compared to web search, where the agent scrapes pages, parses HTML and filters noise, KIRHA uses 95% fewer tokens. See the full comparison on the Benchmark page.
For developers
To explore providers and tools visually, use the Providers Graph. Discovery is the same catalogue, written for agents.