Python orchestration tools for Hanzo AI. The `hanzo` command itself is now a native binary — https://hanzo.sh
Connect Hanzo to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Python orchestration tools for Hanzo AI. The hanzo command itself is now a native binary — https://hanzo.sh. The hanzo mcp server is what makes that connection.
This is the most complete Hanzo SDK — a uv workspace of 60+ composable packages covering the full AI surface: the typed cloud client, an agent framework, the Model Context Protocol server and tools, persistent memory + RAG, distributed compute, and a batteries-included CLI. If you build AI in Python, start here.
hanzoai on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Docs — docs.hanzo.aiIssues — github.com/hanzoai/python-sdk/issuesEmail — support@hanzo.aiflow — what it doesPackage — Purposehanzoai — Typed cloud API client (generated from the Hanzo OpenAPI surface)hanzo — Orchestration helpers and the older Python CLI (console script hanzo-py)hanzo-mcp — Model Context Protocol server — discovers tools via entry pointshanzo-network — Distributed AI compute and node orchestrationhanzo-memory — Persistent memory + RAG (SQLite, optional vector backends)hanzo-tools- — 60+ single-concern tool packages (shell, browser, fs, code, vector, iam, …), each exposing a TOOLS listConfiguration is passed through the environment: HANZO_API_KEY, HANZO_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Hanzo's toolset — Docs, Issues, Email and 8 more — is a fair guide to whether it matches your workflow.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Docs | [docs.hanzo.ai](https://docs.hanzo.ai) |
| Issues | [github.com/hanzoai/python-sdk/issues](https://github.com/hanzoai/python-sdk/issues) |
| support@hanzo.ai | |
| flow | what it does |
| Package | Purpose |
| hanzoai | Typed cloud API client (generated from the Hanzo OpenAPI surface). |
| hanzo | Orchestration helpers and the older Python CLI (console script hanzo-py). |
| hanzo-mcp | Model Context Protocol server — discovers tools via entry points. |
| hanzo-network | Distributed AI compute and node orchestration. |
| hanzo-memory | Persistent memory + RAG (SQLite, optional vector backends). |
| hanzo-tools- | 60+ single-concern tool packages (shell, browser, fs, code, vector, iam, …), each exposing a TOOLS list. |
{
"mcpServers": {
"hanzo": {
"command": "uvx",
"args": ["hanzoai"],
"env": {
"HANZO_API_KEY": "your-value",
"HANZO_BASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| HANZO_API_KEY | Credential the server authenticates with. | Yes |
| HANZO_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.