@cmer/mcp-switchboard vs Cokodo Agent
@cmer/mcp-switchboard is an MCP server published by cmer. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Cokodo Agent is an MCP server published by dinwind. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  @cmer/mcp-switchboard | |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 2.2.1 Downloads/month (npm): 1 296 Downloads/week (npm): 715 Forks (GitHub): 0 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.7.0 Downloads/month (PyPI): 143 Downloads/week (PyPI): 30 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | @cmer/mcp-switchboard | Cokodo Agent |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 5 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-11-04 | Not published |
| Where it runs (differs) | On your machine (@cmer/mcp-switchboard) | On your machine (cokodo-agent) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/cmer/mcp-switchboard | github.com/dinwind/agent_protocol |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
@cmer/mcp-switchboard
Self-hosted MCP switchboard: configure MCP servers once, give each coding agent its own endpoint and its own set of tools.
Cokodo Agent
Serve .agent/ project context, references, and collaborations to MCP-compatible IDEs.
How to run each
@cmer/mcp-switchboard
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Cokodo Agent As a local MCP server: PyPI package
claude mcp add --transport stdio cokodo-agent -- uvx cokodo-agentCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: @cmer/mcp-switchboard · What it can do: Cokodo Agent · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.