MCP Hub
Back to servers

Kunobi MCP Server

Exposes Kunobi's application data and store querying capabilities to AI assistants by bridging stdio to Kunobi's local HTTP MCP endpoint. It features dynamic tool discovery and automatic reconnection to ensure tools like query_store and app_info are always available when Kunobi is running.

Updated
Feb 7, 2026

@kunobi/mcp

MCP server for Kunobi. Runs as a stdio server and connects to Kunobi's built-in HTTP MCP endpoint to expose its tools to AI assistants.

Setup

{
  "mcpServers": {
    "kunobi": {
      "command": "npx",
      "args": ["@kunobi/mcp"]
    }
  }
}

How it works

Claude Code <--stdio--> @kunobi/mcp <--HTTP--> Kunobi (port 3030)
  • Always available: kunobi_status — reports whether Kunobi is installed, running, and reachable
  • Dynamic: When Kunobi is running with MCP enabled, its tools (app_info, query_store, list_stores, etc.) appear automatically via notifications/tools/list_changed
  • Auto-reconnect: If Kunobi is stopped or restarted, tools disappear and reappear without restarting the MCP server

Configuration (optional)

Env varDefaultDescription
KUNOBI_MCP_URLhttp://127.0.0.1:3030/mcpOverride Kunobi's MCP HTTP endpoint

No configuration is required. The server connects to Kunobi's default local endpoint automatically.

Development

pnpm install
pnpm build
pnpm test

For local development against @kunobi/mcp-bundler:

pnpm dev:link    # link local bundler
pnpm dev:unlink  # revert to npm version

Reviews

No reviews yet

Sign in to write a review