mirror of
https://github.com/hanzoai/mcp.git
synced 2026-10-15 12:30:12 +00:00
zeekay
e9a4d37d1f
Rust FFI (rust/src/ffi.rs): - Expose all 13 HIP-0300 tools via C-compatible API - 7 extern "C" functions: init, call_tool, list_tools, last_error, free_string, destroy, version - Persistent multi-threaded tokio runtime behind opaque handle - panic::catch_unwind on all FFI boundaries - Wire 5 missing tools (code, git, fetch, workspace, tasks, hanzo) into ToolRegistry::execute() match arms - Build as cdylib + staticlib (libhanzo_mcp.a / .dylib) Go bindings (go/hanzomcp/): - Handle type with Init/CallTool/CallToolRaw/ListTools/Close - JSON in, JSON out across cgo boundary - runtime.SetFinalizer safety net - 11 tests including 20-goroutine concurrent stress test - Race detector clean TypeScript fixes: - tasks: handle stale todos.json with wrong schema (todos vs items) - code: add symbols + summarize actions for Python parity - fetch: add fetch + head actions for Python parity Results: Rust 66/66 tests, Go 11/11 tests, TS 22/22 conformance
@hanzo/mcp
Model Context Protocol (MCP) server with HIP-0300 unified tool architecture. TypeScript + Rust dual runtime.
Installation
npm install -g @hanzo/mcp
Quick Start
# Start with unified tools (default: 13 HIP-0300 tools)
hanzo-mcp serve
# Legacy individual tools
hanzo-mcp serve --legacy
# With UI extensions
hanzo-mcp serve --enable-ui
# List available tools
hanzo-mcp list-tools
# Install for Claude Desktop
hanzo-mcp install-desktop
HIP-0300 Tool Surface
13 canonical tools organized by axis. Each tool uses action-routed dispatch.
Core Tools (7)
| Tool | Axis | Key Actions |
|---|---|---|
fs |
Bytes + Paths | read, write, stat, list, mkdir, rm, mv, apply_patch, search_text |
exec |
Execution | run, background, ps, kill, logs |
code |
Symbols + Semantics | parse, search, transform, summarize |
git |
Diffs + History | status, diff, log, commit, branch, stash |
fetch |
HTTP/API | get, post, put, delete, download |
workspace |
Project Context | info, config, env, dependencies |
ui |
UI Components | list_components, fetch_component, search, install |
Optional Tools (6)
| Tool | Purpose |
|---|---|
think |
Structured reasoning |
memory |
Persistent storage |
hanzo |
Hanzo platform API (iam, kms, paas, commerce) |
plan |
Task planning |
tasks |
Task tracking |
mode |
Developer modes |
Usage
CLI Options
# Default: HIP-0300 unified surface (13 tools)
hanzo-mcp serve
# Legacy individual tools (read_file, write_file, bash, etc.)
hanzo-mcp serve --legacy
# Enable UI extensions
hanzo-mcp serve --enable-ui --enable-desktop
# Disable specific tools
hanzo-mcp serve --disable-tools plan,tasks
Programmatic Usage
import { getConfiguredTools } from '@hanzo/mcp';
// HIP-0300 unified surface (default)
const tools = getConfiguredTools({ unified: true });
// Legacy individual tools
const tools = getConfiguredTools({ enableLegacy: true });
// With UI extensions
const tools = getConfiguredTools({
unified: true,
enableUI: true,
enableDesktop: true,
});
AI Client Configuration
Claude Desktop / Cursor
Add to .mcp.json:
{
"mcpServers": {
"hanzo": {
"command": "npx",
"args": ["@hanzo/mcp", "serve"]
}
}
}
Architecture
src/tools/unified/ # HIP-0300 action-routed tools (fs, exec, code, fetch, workspace, hanzo)
src/tools/ # Individual tools (git, think, memory, tasks, plan, mode, etc.)
rust/src/tools/ # Rust native tools (exec, git, fetch, code, computer, etc.)
The Rust runtime provides native performance for latency-sensitive operations (<5ms clicks, <2ms keypress, <50ms screenshots).
Python SDK Parity
The Python implementation (hanzo-mcp on PyPI) exposes the same 13 HIP-0300 tools via entry-point discovery from hanzo-tools-* packages. Tool names and action schemas are identical across both runtimes.
pip install hanzo-mcp
License
MIT