A side-by-side look at the Baton and Routed MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Baton for coding agents work as a local process; choose Routed for coding agents. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Baton when
You need dedicated capabilities in the Coding Agents domain.
No tool names declared yet. Check the project README from the listing page.
Routed tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
No confirmed install command for Routed yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Baton is categorized under Coding Agents and uses a local stdio subprocess. Routed belongs to Coding Agents and uses an install path we have not confirmed yet. Pick Baton for coding agents work and Routed for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Routed has no confirmed install command yet — follow its own setup instructions.
Baton has no declared pricing — check the project's own site. Routed is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add baton-2 and bshea-1-routed as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Baton has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 27 GitHub stars. Routed has 47/100 (Fair) with 0 views, 0 installs and 24 GitHub stars.