A router that cuts MCP tool clutter to save agent tokens
MCP-Dynamic-Router is a gateway that keeps AI agents from reading every MCP tool definition on every turn. The usual MCP setup often loads all connected servers and tool descriptions into Claude’s . A 200,000-token can fit a lot, but sending 100 every time can make costs much higher than needed.
Too many unused can also make the model choose tools less reliably and invent wrong arguments for tool calls. Another production problem is that tools cannot be added or removed during a session without reloading the whole context. MCP-Dynamic-Router tries to solve this by showing Claude only the 2 or 3 tools that fit the current job.
For voice and chat systems, it can route partial speech while the person is still talking, warm up connections, and prefetch . It can also skip heavier routing when a request exactly matches a tool description, and it can return a clarify or no_tool decision instead of forcing a bad tool call.
Key points
- Sending every MCP tool definition on every turn can raise costs.
- Large tool lists can make the model less accurate at choosing tools and filling arguments.
- MCP-Dynamic-Router aims to expose only the 2 or 3 relevant tools for a task.
- Voice and chat systems can use partial speech to prepare safe early.
- The router can choose clarify or no_tool instead of forcing a wrong tool call.