MCP

One Model Context Protocol server, one tool surface. Add hanzo-mcp to Claude Code (or Cursor, Claude Desktop, or any MCP client) and every Hanzo capability shows up through a single connection — no per-tool wiring.

claude mcp add hanzo -- npx -y --package=@hanzo/mcp@latest hanzo-mcp serve

Name the package and the binary separately. In the shorter npx -y @hanzo/mcp serve, npx is free to read serve as a second package to fetch.

That one command exposes the full surface:

• 13 unified tools — fs, exec, code, git, fetch, workspace, ui, plus optional think, memory, hanzo, plan, tasks, mode. One action-routed tool per capability (HIP-0300), so the client sees a small, stable set instead of hundreds of overlapping names.
• Cloud services — the hanzo tool routes to your platform natively: IAM (identity), Commerce, Storage, and the AI API at api.hanzo.ai/v1, authenticated with your token.
• Your connectors — GitHub, Slack, Google, Discord, X, and more, surfaced through the same connection once linked in the console.

The same surface ships three ways — TypeScript (@hanzo/mcp), Python (hanzo-mcp on PyPI), and Rust (hanzo-mcp::brain) — mirrored 1-to-1, over the MCP stdio and streamable-http transports.

Client setup

{
  "mcpServers": {
    "hanzo": {
      "command": "npx",
      "args": ["-y", "--package=@hanzo/mcp@latest", "hanzo-mcp", "serve"]
    }
  }
}

Sign in once (hanzo auth login) and the hanzo cloud tool + your connectors authenticate automatically; the local tools (fs, exec, git, …) work with no account.

The tool index

Every tool the platform can expose is indexed at GET api.hanzo.ai/v1/tool (authenticated). The unified server presents them through the compact action-routed surface above. A tool's source is one of six values, and the order below is also the precedence order — the lowest wins a name collision:

Adding a source of your own is Extend.

Connectors

Everything Hanzo can connect to, by how you connect it — native connectors you link once in the console (GitHub App, OAuth2), and the open MCP ecosystem indexed live from the official registry. Search across both.

MCP as a Service

Beyond the unified server, Hanzo can also host any MCP server for you — deploy from any npx, uvx, or custom package with instant scaling and zero infrastructure to manage.

hanzo mcp launch npx @modelcontextprotocol/server-filesystem

Key Capabilities

• Any MCP server — Filesystem, Git, SQL, KV, Slack, GitHub, Notion, and more
• 1-click Deploy — Launch any MCP server with a single command
• Auto Scaling — Scale from 0 to thousands of instances automatically
• $0 Idle Cost — Pay only for what you use, no idle charges
• Secure Sandboxing — Isolated containers with fine-grained permissions
• 15+ Regions — Edge deployment for lowest latency globally

Launch Methods

NPX Packages

hanzo mcp launch npx @modelcontextprotocol/server-filesystem
hanzo mcp launch npx @modelcontextprotocol/server-github
hanzo mcp launch npx @modelcontextprotocol/server-slack

UVX / Python

hanzo mcp launch uvx mcp-server-sqlite
hanzo mcp launch uvx mcp-server-postgres

Custom Servers

hanzo mcp launch git://github.com/you/mcp-server
hanzo mcp launch docker://your-org/mcp-custom:latest

Configuration

Deploy multiple servers with a single config file:

version: "1"
servers:
  filesystem:
    package: "@modelcontextprotocol/server-filesystem"
    runtime: npx
    args: ["/workspace"]

  database:
    package: "mcp-server-postgres"
    runtime: uvx
    env:
      DATABASE_URL: "${secrets.DATABASE_URL}"

  github:
    package: "@modelcontextprotocol/server-github"
    runtime: npx
    env:
      GITHUB_TOKEN: "${secrets.GITHUB_TOKEN}"

  custom:
    image: "your-org/mcp-custom:latest"
    runtime: docker
    replicas: 3

hanzo mcp deploy

Enterprise Features

Available Tools

Next Evolution: ZAP

MCP made tool integration easy. ZAP makes it fast. Zero-Copy Agent Protocol is the next evolution: zero-copy serialization, 40-50x lower overhead, built for agent swarms at scale.

ZAP includes MCP Gateway Mode for seamless migration.