Kuuhaku

dev.kuuhakuPublished by kuuhaku.devOfficial publisherv0.2.10Updated Oct 24, 2026

Ask who calls a route, what a change breaks or who reads a field, across a system's repos.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Kuuhaku lets an assistant answer cross-repository questions about a system, such as who calls a route, what a change breaks, or who reads a field.

What you can do
Kuuhaku is a remote MCP server, also runnable locally via the npm package kuuhaku with npx, that answers questions spanning a system's repositories. According to its registry description, it can tell who calls a route, what a change breaks, and who reads a field. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Use it when you need impact analysis or dependency tracing across several repositories, for example before changing an API route or a shared data field and wanting to know which callers or readers are affected. It is aimed at teams whose code is spread over multiple repos.
Requirements
Either connect to the remote endpoint at api.kuuhaku.dev over streamable HTTP, or run the npm package kuuhaku locally with npx over stdio. Authentication is required: a bearer token sent in the Authorization header, described as the workspace's push token, obtained from the CLI page of the app. No environment variables are declared.
Before you install
The server requires a bearer credential in the Authorization header, described as the workspace's push token; treat it as a secret and avoid exposing it in logs or shared configuration. The manifest does not document which repositories or data the server reads or sends to the remote service, so review that before pointing it at private code.

Installation

In SourceWeft

  1. Open Kuuhaku in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.kuuhaku%2Fkuuhaku/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "kuuhaku": {
      "type": "http",
      "url": "https://api.kuuhaku.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

2
  1. v0.2.10LatestOct 22, 2026
  2. v0.2.9Oct 15, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.