mcp-debugger vs CapabilityWire
mcp-debugger lists no tools and runs locally and CapabilityWire lists no tools and runs remotely.
| Fact | mcp-debuggerio.github.debugmcp/mcp-debugger | CapabilityWireio.github.jawauntb/capabilitywire |
|---|---|---|
| Score | Not checked yet | Not checked yet |
| Status | Not checked yet | Not checked yet |
| Tools | 0 | 0 |
| Can write data | No tools listed | No tools listed |
| Runs | Local | Remote |
| Needs first | Node.js | – |
| Licence | MIT | Not stated |
| Latest version | 0.25.1 | 0.1.1 |
| Known advisories | 0 | Not checked yet |
| Works in | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, mcp-client-cli, oterm, TUUI, BoltAI, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, oterm, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI |
| Downloads last week | Not known | Not known |
| Install | Install mcp-debugger | Install CapabilityWire |
Scores and status come with our own checks, which have not run on these servers yet. The rest is from the publishers' registry entries, package registries and advisory databases.
Compare mcp-debugger with othersCompare CapabilityWire with others