Hatago Mcp Hub
Register one MCP hub so your coding agent can discover, route, and manage many MCP servers from a single stdio connection instead of juggling separate configs.
Overview
Hatago MCP Hub is a MCP server for the Build phase that unifies management and access to multiple Model Context Protocol servers through one stdio hub.
What is this MCP server?
- Unified hub for managing multiple Model Context Protocol servers from one entry point
- Stdio transport via npx (@himorishige/hatago-mcp-hub) for Claude Code, Cursor, and similar hosts
- Reduces duplicated MCP client configuration when your stack grows past a handful of servers
- Published server schema v2025-09-29; package version 0.0.16 on npm
- Open-source on GitHub (himorishige/hatago-mcp-hub) for self-hosted or registry-based install
- Server version 0.0.16
- Stdio transport via npm package @himorishige/hatago-mcp-hub
- Runtime hint: npx
Community signal: 28 GitHub stars.
What problem does it solve?
Every new MCP server adds another config entry and connection, which makes agent setups brittle and hard to maintain as your toolchain grows.
Who is it for?
Indie builders running three or more MCP servers who want a single hub-style control point during local agent development.
Skip if: Teams that only need one MCP server or want fully managed cloud MCP hosting with no local stdio wiring.
What do I get? / Deliverables
After install, you register one hub in your agent config and consolidate how multiple MCP backends are managed instead of editing many separate server blocks.
- Single registered MCP hub entry replacing or simplifying multiple server configs
- Centralized routing layer for additional MCP backends as you add them
- Reproducible npm-based install path (version 0.0.16) for team sharing
Recommended MCP Servers
Journey fit
MCP server orchestration is core agent infrastructure while you assemble integrations during the product build phase. Hatago sits alongside other agent-tooling MCPs as the control plane for multiple protocol servers, not a feature-facing integration.
How it compares
MCP orchestration hub, not a single-purpose integration or Claude skill.
Common Questions / FAQ
Who is Hatago MCP Hub for?
Solo builders and developers who run several MCP servers in Claude Code, Cursor, or Codex and want one unified hub instead of many parallel stdio configs.
When should I use Hatago MCP Hub?
Use it during the build phase when you are expanding agent integrations and need centralized management as your MCP catalog grows.
How do I add Hatago MCP Hub to my agent?
Add the npm package @himorishige/hatago-mcp-hub to your MCP config with stdio transport and runtimeHint npx, then point your agent at the published server definition from the MCP registry or GitHub repo.