# MCP

URL: https://docs.hanzo.ai/docs/mcp

> The unified Hanzo MCP — one server that gives Claude Code, Cursor, and any MCP client a single tool surface plus your connected cloud services.

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.

> Looking for the hosted MCP server instead? \*\*[Cloud MCP](https://docs.hanzo.ai/docs/mcp-tools)\*\* is a URL with nothing to install, and its every tool is enumerated in the [tool catalogue](https://docs.hanzo.ai/docs/mcp-tools/all-tools). This page is the server that runs beside your editor.

```bash title="Add the Hanzo MCP to Claude Code"
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

```json title="Claude Desktop / Cursor — mcp config"
{
  "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](https://docs.hanzo.ai/docs/extend#precedence--who-wins-a-name-collision) — the lowest wins a name collision:

| Source        | What it is                                                       |
| ------------- | ---------------------------------------------------------------- |
| `connector`   | Linked cloud integrations (GitHub, Slack, Google, Discord, X, …) |
| `function`    | User-defined functions                                           |
| `zap-service` | First-party cloud service routes                                 |
| `agent`       | Agent entry points                                               |
| `skill`       | Packaged skills — listing only, never called                     |
| `mcp`         | Tools on your org's own registered MCP servers                   |

Adding a source of your own is [Extend](https://docs.hanzo.ai/docs/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](https://registry.modelcontextprotocol.io). Search across both.

The live connector catalogue: [the MCP registry](https://registry.modelcontextprotocol.io)

---

## 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.

```bash title="Launch an MCP server"
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

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

### UVX / Python

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

### Custom Servers

```bash
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:

```yaml title="mcp-config.yaml"
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
```

```bash
hanzo mcp deploy
```

## Enterprise Features

- **Managed Hosting**: Deploy to Hanzo Cloud with auto-scaling and monitoring
- **Secure Sandboxing**: Isolated containers with fine-grained permissions
- **Edge Deployment**: 15+ global regions for lowest latency
- **Version Control**: Pin versions, rollback instantly, audit trails
- **Tool Federation**: Combine multiple MCP servers into unified endpoints
- **Config Management**: Centralized secrets and environment variable management

## Available Tools

| Category          | Tools                                      |
| ----------------- | ------------------------------------------ |
| **Storage**       | Filesystem, S3, Google Drive, Notion       |
| **Databases**     | SQL, MySQL, SQLite, KV, DocumentDB         |
| **Dev Tools**     | Git, GitHub, GitLab, Linear, Jira          |
| **Communication** | Slack, Discord, Email, Twilio              |
| **Cloud**         | AWS, GCP, Azure, Kubernetes                |
| **AI/ML**         | Hugging Face, Weights & Biases, MLflow     |
| **Web**           | Browser automation, Puppeteer, Screenshots |
| **Custom**        | Any Docker container or npm/pip package    |

## 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.

- [ZAP Protocol](https://docs.hanzo.ai/docs/zap): 10-100x faster, post-quantum secure
- [Gateway Service](https://docs.hanzo.ai/docs/openapi/gateway): One API for every model

- [Documentation](https://docs.hanzo.ai/docs): The AI operating system for business. Building business software since 2014. Techstars '17. Every model, every tool, one key — in our cloud or on your own machine.
- [Agents: start here](https://docs.hanzo.ai/docs/agents): Sign up free with a wallet. Get an API key free. A small free allowance to try it. Top up in USDC or USDT over the API to raise your limits and pay as you go. No human required.
- [Quickstart](https://docs.hanzo.ai/docs/quickstart): Install the CLI, log in, and make your first call — then see that same call as an SDK method, raw HTTP and an MCP tool.
- [Models](https://docs.hanzo.ai/docs/models): Enso routes, Kai decides, Zen reasons, Policy governs — the model families, what each is for, and the live catalogue with every id you can pass.
- [Cloud MCP](https://docs.hanzo.ai/docs/mcp-tools): One JSON-RPC endpoint that gives any MCP client 120 tools over the Hanzo cloud, plus the external servers your org registers.
- [Extend](https://docs.hanzo.ai/docs/extend): Add a tool to Hanzo three ways — a Go provider inside the fleet, your own MCP server, or an auto connector. The contract all three land on, and how to choose.
- [Capabilities](https://docs.hanzo.ai/docs/openapi): Every Hanzo capability — 131 of them, 2481 operations, generated from the OpenAPI document.
- [SDKs](https://docs.hanzo.ai/docs/sdks): One generated client per language for the whole /v1 surface, plus the hand-written AI and per-service libraries for TypeScript. What each one is called on its registry, and the same first call in each.
- [CLI](https://docs.hanzo.ai/docs/cli): The \`hanzo\` command line — 2263 commands across 121 capabilities, generated from the CLI's own command table.
- [Coding agents](https://docs.hanzo.ai/docs/coding): Run Hanzo Dev, Claude Code, Codex, Cursor, Gemini CLI, Qwen Code, OpenCode, Goose, Hermes and more from one command, with Enso and Kai a tool call away.
- [Guides](https://docs.hanzo.ai/docs/guides): One task per page, each written four ways: a CLI command, an SDK call, an HTTP request and an MCP tool.
- [Hello](https://docs.hanzo.ai/docs/guides/hello): Identity — prove the key works and print who it belongs to.
- [Chat](https://docs.hanzo.ai/docs/guides/chat): One completion.
- [Money](https://docs.hanzo.ai/docs/guides/money): Balance, then the usage that moved it.
- [Store](https://docs.hanzo.ai/docs/guides/store): KV round-trip — create a store, read it back, delete it.
- [Agent](https://docs.hanzo.ai/docs/guides/agent): Create an agent, run it, read the run back.
- [Tools](https://docs.hanzo.ai/docs/guides/tools): List the MCP tools this key can reach.
- [Integrations](https://docs.hanzo.ai/docs/guides/integrations): Point any agent framework at Hanzo. One host, one key, two lines — and the exact parameter name for each of sixteen frameworks.
- [Migrate](https://docs.hanzo.ai/docs/guides/migrate): 45 vendors and tools, each mapped to the Hanzo capability that answers it — how to start, nouns, the call before and after, and what does not carry.
- [Concepts](https://docs.hanzo.ai/docs/concepts): Seven ideas the whole API is built out of — tenancy, projects, sandboxes, agents, budgets, memory and workflows.
- [Self-improvement](https://docs.hanzo.ai/docs/self-improvement): How everyday use can improve Hanzo's memory, skills, tools, connectors, apps and agent harness through a continuous, validated feedback loop.
- [Glossary](https://docs.hanzo.ai/docs/glossary): One name per idea, and the names other systems use for the same idea. Read the second column when a word here does not match the word you arrived with.
- [Architecture](https://docs.hanzo.ai/docs/architecture): How Hanzo Cloud is built today, and the plugin-platform direction it is evolving toward.
- [The Network](https://docs.hanzo.ai/docs/network): The AI cloud you can run yourself. hanzo.network is hanzod nodes that spawn the same unified cloud binary we run in production — OSS AI cloud in one binary, BYO GPU or K8s, mine on any device, free for public and open-source workloads.
- [ZAP Protocol](https://docs.hanzo.ai/docs/zap): Zero-Copy App Proto — High-performance Cap'n Proto RPC for AI agent communication. 10-100x faster than MCP with post-quantum security.
- [Hanzo Dev](https://docs.hanzo.ai/docs/dev): AI-powered coding assistant for your terminal. Install, configure, and operate Hanzo Dev.
- [Environments](https://docs.hanzo.ai/docs/environments): An environment is derived from the apps that point at it — there is nothing to create. How production, staging and previews actually work.
- [Testnet and devnet](https://docs.hanzo.ai/docs/testnet): Two copies of the Hanzo cloud that take only Square sandbox cards. Testnet runs exactly what production runs; devnet runs what is being built next, with accounts of its own.
- [Events](https://docs.hanzo.ai/docs/events): One ingest endpoint that dispatches on the shape of the body, what each credential may write, and the receipt every wire gets back.
- [Webhooks](https://docs.hanzo.ai/docs/webhooks): Register an https endpoint, pick events by subject wildcard, and verify the HMAC signature on every delivery.
- [Credits & billing](https://docs.hanzo.ai/docs/credits): What a credit is, how a call draws one down, where the balance lives, and what happens when it reaches zero.
- [Pricing](https://docs.hanzo.ai/docs/pricing): What a request costs — the Enso tiers, per-token billing for every other model, and the per-call rates for tools, images and audio.
- [Error codes](https://docs.hanzo.ai/docs/errors): Every error code Hanzo Index can return, with its HTTP status and type. The \`link\` in an error body points here.
- [Workspace](https://docs.hanzo.ai/docs/workspace): Build sheet for the Hanzo workspace — layout, dimensions, and the Slack part each piece answers to.
- [Console](https://docs.hanzo.ai/docs/console): The Hanzo Cloud console at platform.hanzo.ai -- manage every product, key, and organization from one app.
- [Hanzo Chat](https://docs.hanzo.ai/docs/chat): The chat app on Hanzo Cloud — enso and Zen models, MCP tools, agents, file uploads and RAG. Hosted at chat.hanzo.ai, or self-host it.
- [Integrations & Extensions](https://docs.hanzo.ai/docs/apps): Install and connect Hanzo across your browser, editor, desktop, docs, design tools, and business apps — one API key, one identity, everywhere.
- [Usage](https://docs.hanzo.ai/docs/usage): One usage plane for every AI account you have — rate limits, credits, and spend, across Hanzo and the other providers you already pay for.
- [Referral & Affiliate Program](https://docs.hanzo.ai/docs/referrals): Earn 15% recurring revenue share for 12 months while giving referred builders $20 in free cloud credits.
- [Startups](https://docs.hanzo.ai/docs/startups): Up to $150,000 in Hanzo Cloud credits for venture-backed startups -- plus $5 free for everyone and bring-your-own-compute.
- [Run your org](https://docs.hanzo.ai/docs/run-your-org): From signup to a running brain, team, and bot for your organization — under ten minutes.
- [Authentication](https://docs.hanzo.ai/docs/api-keys): How a request proves who it is — the two Hanzo key types, which one may ship in a browser, and how to create, limit, edit and revoke keys.
- [About Hanzo](https://docs.hanzo.ai/docs/about/company): The AI operating system for business. Building business software since 2014. Techstars '17.