Kirha MCP

Kirha exposes a remote MCP server at mcp.kirha.com. Any client that supports the Model Context Protocol can connect to it directly, no local process needed.

Option 1: MCP Installer CLI (recommended)

The fastest way to get started. The @kirha/mcp-installer package auto-detects your client and writes the config for you.

npx @kirha/mcp-installer install --client claudecode --key KIRHA_API_KEY

npx @kirha/mcp-installer install --client opencode --key KIRHA_API_KEY

npx @kirha/mcp-installer install --client codex --key KIRHA_API_KEY

npx @kirha/mcp-installer install --client droid --key KIRHA_API_KEY

npx @kirha/mcp-installer install --client gemini --key KIRHA_API_KEY

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 gemini

Option 2: Manual config

Add the Kirha MCP server to your client configuration file manually.

{
  "mcp": {
    "kirha": {
      "type": "remote",
      "url": "https://mcp.kirha.com",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer KIRHA_API_KEY"
      }
    }
  }
}

{
  "mcp": {
    "kirha": {
      "type": "remote",
      "url": "https://mcp.kirha.com",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer KIRHA_API_KEY"
      }
    }
  }
}

Exposed tool

The MCP server exposes a single Search tool. Its description tells the agent:

Search across Kirha's premium real-time data verticals. Each vertical groups multiple specialized providers that Kirha intelligently composes and orchestrates to deliver the best context for your domain-specific query. Check https://discovery.kirha.com/home.mdx for an overview of available verticals, providers and their capabilities.

Notice the link to discovery.kirha.com in the tool description. When the agent reads this page, it learns which verticals exist, what providers each vertical includes, and what kind of queries work best. This means the agent picks the right vertical on the first try instead of guessing.

You might think this extra read costs more tokens, but it's the opposite. Kirha returns structured, domain-specific data directly from premium providers. Compared to web search, where the agent scrapes pages, parses HTML, and filters noise, Kirha uses 95% fewer tokens while delivering more accurate results. See the full comparison on the Benchmark page.