Skip to content

Tags: hanzoai/mcp

Tags

rust-v1.1.23

Toggle rust-v1.1.23's commit message
initialize is a negotiation, so answer the revision the client asked for

The server replied "2024-11-05" to every initialize, whatever the client asked
for. `hanzo dev` asks for 2025-06-18 and refuses a server that answers anything
else, so it reported `MCP server hanzo failed to start` — in an image where the
binary was on PATH, `dev mcp list` showed it registered, and a hand-written
handshake got 29 tools back. Everything that looked at the server passed;
nothing that PAIRED it with an agent worked.

Negotiation is the whole fix: echo the requested revision when it is one we
serve, answer our newest when it is not and let the client decide. The three
listed revisions are the ones this server can actually serve — initialize,
tools/list and tools/call are unchanged across them, and what the later ones add
is optional and unadvertised. A client pinned to the original revision keeps
getting it, which is the point of negotiating rather than moving the constant.

go/v0.1.1

Toggle go/v0.1.1's commit message
go/v0.1.1 — zip v1.9.0

github.com/hanzoai/mcp/go off the dead github.com/hanzoai/zip fork and on
zap-proto/zip v1.9.0 / zap-proto/http v0.2.2. v0.1.0 still pinned the fork,
so this is the first release a consumer can take without it.

Claude-Session: https://claude.ai/code/session_01Azk4cknLD2FJYYaaVZ4yXP

rust-v1.1.15

Toggle rust-v1.1.15's commit message
hanzo-mcp 1.1.15

v2.5.0

Toggle v2.5.0's commit message
feat: cloud.Mount per HIP-0106 (Go path at mcp/go)

go/v0.1.0

Toggle go/v0.1.0's commit message
feat(go): first release — cloud.Mount per HIP-0106

v2.4.3

Toggle v2.4.3's commit message
fix(ci): pin amd64 + add id-token permission

The shared docker-build.yml defaults to linux/amd64,linux/arm64. The
hanzo-build-linux-arm64 ARC scale set is paused (DOKS has no arm64
droplets). Pin to amd64 only so the build doesn't sit queued forever.

Also add id-token: write — the reusable workflow's job-level
permission can't elevate above the caller's top-level ceiling.

v2.4.1

Toggle v2.4.1's commit message
v2.4.1 — HIP-0300 bidirectional action parity

v2.4.0

Toggle v2.4.0's commit message
feat(zap): 100% MCP/ZAP protocol parity with method pass-through v2.4.0

- Add McpMethodHandler type and handleMethod option to ZAP server
- Refactor MCP handlers into reusable functions shared between MCP + ZAP
- CLI now starts ZAP server alongside stdio with full method dispatch
- All MCP methods (tools/*, resources/*, prompts/*) work identically over ZAP
- Fix TS strict mode error in code.ts summarize action
- 337/337 tests pass

v2.3.0

Toggle v2.3.0's commit message
feat(zap): ZAP WebSocket server for browser extension discovery

v2.2.0

Toggle v2.2.0's commit message
fix: resolve CI test failures on Ubuntu

- Use seq instead of brace expansion for shell large output test (sh compat)
- Handle platform-dependent behavior in search error test (rg vs grep)