Agent MCP Router
Agent MCP Router MCP is a MCP server that routes agent tool calls to 62 MEOK MCP backends through one namespaced stdio entry.
About
Agent MCP Router MCP is a stdio Model Context Protocol server that acts as one front door for a large MEOK tool fleet—documented as holding 62 MEOK MCPs behind a single namespaced interface. developers drowning in separate MCP entries in Claude Code or Cursor install the router to keep one process, one config block, and predictable tool prefixes instead of maintaining dozens of parallel stdio launches. It belongs in the build phase under integrations: you add it when your agent product or personal dev stack depends on many MEOK servers and you want centralized routing rather than re-implementing discovery in every project. The router does not replace individual MCP implementations; it delegates to them. Expect Python, PyPI install, and alignment with whatever namespace conventions MEOK publishes. Intermediate complexity reflects fleet wiring and debugging routed calls across many downstream servers.
- Single MCP router fronting the MEOK fleet with namespaced tool routing
- Catalog description references 62 MEOK MCPs aggregated behind one server
- Stdio transport via PyPI package agent-mcp-router-mcp v1.1.1
- Reduces MCP config sprawl for Claude Code, Cursor, and Codex setups
- Version 1.1.1 on MCP server schema 2025-12-11
Agent MCP Router by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
claude mcp add agent-mcp-router-mcp -- uvx agent-mcp-router-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | agent-mcp-router-mcp |
|---|---|
| Transport | STDIO |
| Auth | None |
What it does
Expose dozens of MEOK MCP backends through one namespaced router so your agent config stays a single stdio entry.
Who is it for?
Best when you're standardizing on MEOK’s MCP ecosystem and want one router instead of a long mcp.json list.
Skip if: Projects that need only one or two unrelated MCP servers with no MEOK dependency.
What you get
After registration, your agent talks to one router MCP that namespaces and forwards calls across the MEOK fleet you enable.
- One consolidated MCP server entry replacing many per-tool stdio configs
- Namespaced tool surface reachable from your agent session
By the numbers
- Described as holding 62 MEOK MCPs behind one namespaced router
- Package version 1.1.1 with stdio transport on PyPI
Recommended MCP Servers
0pi MCPFree, 2hr expiry agent storage to cache contexts, bridge workflows, or dump data.
100Hires AI ATS & Recruitment Software MCPOfficial 100Hires MCP: AI ATS & Recruitment Software for candidates, jobs, applications, interviews.123elec MCPInterface MCP officielle du site marchand 123elec, catalogue, stock, panier, commandes.
1stay MCPHotel booking MCP server.2
2D Assets MCPMCP server for generating advanced mock 2D PNG assets for game prototypes.43D MeshWeaver MCPMesh spatial optimizer reducing geometric overhead in 3D assets.How it compares
MCP fleet router and namespace gateway, not a standalone domain skill like negotiation or orchestration.
FAQ
Who is agent-mcp-router-mcp for?
It is for developers and small teams running MEOK-heavy agent stacks who need one MCP entry instead of configuring dozens of separate stdio servers.
When should I use agent-mcp-router-mcp?
Use it during build when you are integrating multiple MEOK MCP tools and want namespaced routing from a single router process.
How do I add agent-mcp-router-mcp to my agent?
Install agent-mcp-router-mcp from PyPI, register it as a stdio MCP server in your host, and point router settings at the MEOK MCP instances you want in the fleet.