Hanzo MCP · Tool server

An MCP server with thirteen tools

It gives a model a shell, a filesystem, a code index, git, HTTP, and your project's own context, over stdio or streamable HTTP. Point any MCP client at it and the tools show up.

Read the docs View on GitHub

Open source, MIT. Same tool names and schemas in TypeScript, Python, and Rust — one API, three runtimes.

Available throughClaude DesktopClaude CodeCursorAny MCP client

A catalog of 260 collapsed into 13

fs for bytes and paths. exec for processes. code for symbols. git for history. fetch for HTTP. workspace for the project you are in. ui for components. Six more — think, memory, plan, tasks, mode, and the Hanzo platform itself — are there when you want them.

Paste and ship

Paste this into any agent. It reads the skill manifest and calls MCP from there.

Agent prompt

Read https://hanzo.ai/skill.md and use Hanzo MCP in my project. Start with: hanzo mcp create

The tools

What each one does

Every tool takes an action and the arguments that action needs. These are the verbs.

fs

read, write, stat, list, mkdir, rm, mv, apply_patch, search_text. Bytes and paths, including the patch verb an agent needs to edit a file it did not write whole.

exec

run, background, ps, kill, logs. A command that outlives the call goes to background and you read it back through logs, so a dev server does not hold the turn open.

code

parse, search, transform, summarize. Search by symbol rather than by string, so renaming a function finds the callers and not the comments that mention it.

git and fetch

git does status, diff, log, commit, branch, stash. fetch does get, post, put, delete, download — the ordinary HTTP verbs, plus the one that writes the body to a file.

workspace, think, memory

workspace answers info, config, env, dependencies about the project you are actually in. think records structured reasoning. memory persists past the session.

ui, plan, tasks, mode, hanzo

ui lists, searches, fetches and installs components. plan and tasks hold the work. mode switches presets. hanzo reaches IAM, KMS, PaaS, and Commerce.

Get started

One config block

Use the --package= form. Without it npx resolves "serve" as a separate package and runs an unrelated static-file server instead — on every platform.

json

// .mcp.json — add Hanzo MCP to any MCP client
{
  "mcpServers": {
    "hanzo": {
      "command": "npx",
      "args": ["-y", "--package=@hanzo/mcp", "hanzo-mcp", "serve"]
    }
  }
}

// Or install it and run the server yourself:
//   npm install -g @hanzo/mcp && hanzo-mcp serve
//   hanzo-mcp list-tools
//   hanzo-mcp install-desktop

Read the docs View on GitHub

Add it to your client

One block in .mcp.json, or install the binary and run hanzo-mcp serve yourself.

GitHub Hanzo Platform

MCP

MCP docs →