by hanzoai
Hanzo secures codebase interactions with file ops, command execution, project analysis and Jupyter notebook management u
A comprehensive MCP server providing 54 development tools including file operations, shell commands, UI component management, and GUI automation. Offers flexible configuration to enable/disable tool categories as needed.
Hanzo is a community-built MCP server published by hanzoai that provides AI assistants with tools and capabilities via the Model Context Protocol. Hanzo secures codebase interactions with file ops, command execution, project analysis and Jupyter notebook management u It is categorized under developer tools.
You can install Hanzo in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Hanzo is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
I recommend Hanzo for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Hanzo is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Hanzo has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We evaluated Hanzo against two servers with overlapping tools; this profile had the clearer scope statement.
Strong directory entry: Hanzo surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We evaluated Hanzo against two servers with overlapping tools; this profile had the clearer scope statement.
We wired Hanzo into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
According to our notes, Hanzo benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Hanzo has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Useful MCP listing: Hanzo is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 35
Unified Model Context Protocol (MCP) server providing comprehensive AI development tools and UI component management.
npm install -g @hanzo/mcp
# Start with all tools enabled (default: 54 tools)
hanzo-mcp serve
# Core tools only (19 tools)
hanzo-mcp serve --core-only
# Disable specific tool categories
hanzo-mcp serve --disable-ui # Exclude UI tools
hanzo-mcp serve --disable-autogui # Exclude AutoGUI tools
hanzo-mcp serve --disable-orchestration # Exclude orchestration tools
# List all available tools (54 by default)
hanzo-mcp list-tools
# Install for Claude Desktop
hanzo-mcp install-desktop
Disable with --disable-ui flag:
Disable with --disable-autogui flag:
Disable with --disable-orchestration flag:
# All tools enabled (default - 54 tools)
hanzo-mcp serve
# Core tools only (19 tools)
hanzo-mcp serve --core-only
# Disable specific categories
hanzo-mcp serve --disable-ui --disable-autogui --disable-orchestration
# Custom tool selection
hanzo-mcp serve --enable-categories files,ui --disable-tools bash,shell
# List tools by category
hanzo-mcp list-tools --category ui
import { createMCPServer } from '@hanzo/mcp';
// Basic server with core tools
const server = await createMCPServer();
// Server with UI tools enabled
const serverWithUI = await createMCPServer({
toolConfig: {
enableCore: true,
enableUI: true
}
});
// Custom configuration
const customServer = await createMCPServer({
name: 'my-mcp-server',
version: '1.0.0',
toolConfig: {
enableCore: true,
enableUI: true,
enableAutoGUI: true,
enableOrchestration: true,
disabledTools: ['bash'],
customTools: [/* your tools */]
}
});
Add to .mcp.json:
{
"mcpServers": {
"hanzo": {
"command": "npx",
"args": ["@hanzo/mcp", "serve"]
}
}
}
Add to .cursor/mcp.json:
{
"mcpServers": {
"hanzo": {
"command": "npx",
"args": ["@hanzo/mcp", "serve"]
}
}
}
MIT © Hanzo AI
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.