Tool routing middleware for Claude Code and MCP servers.
Middleware layer that coordinates Model Context Protocol servers for Claude Code. Routes tool calls to the right MCP server, handles connection management, and recovers from failures automatically. The layer that keeps the entire MGT AI stack running cleanly.
MCP
Type
Protocol middleware
Tool Router
Function
Multi-server coordination
Active
Status
Running in production
Context
Claude Code can connect to multiple MCP servers at once, each providing a different set of tools. Neon for database operations. Chrome DevTools for browser automation. Stitch for UI generation. Without coordination, managing which server handles which request becomes brittle.
The coordinator sits between Claude Code and the MCP server pool. When a tool call comes in, it routes to the correct server, manages the connection lifecycle, and handles any errors without dropping the session. Claude Code stays focused on the task.
Built in two weeks as infrastructure, not a product. The goal was zero maintenance overhead. It either works or it recovers automatically.
What We Built
Inspects incoming tool calls and routes each to the appropriate MCP server based on tool name and capability mapping. No manual configuration per session.
Maintains persistent connections to each MCP server. Detects drops and reconnects automatically. Claude Code never sees a dead connection mid-task.
When a server call fails, the coordinator retries with backoff, falls back to an alternate server where possible, and surfaces clean errors to Claude Code.
Tracks which tools each connected server exposes. When a new MCP server is added to the pool, its tools are registered automatically without config changes.
Connected servers
Tech Stack
If you are integrating AI tooling into your workflows and the plumbing is getting complicated, we build the coordination layer that makes it simple.