Chrome DevTools MCP vs Cobrowser
Chrome DevTools MCP lists no tools and runs locally and Cobrowser lists no tools.
| Fact | Chrome DevTools MCPio.github.secforge/chrome-devtools-mcp | Cobrowserio.github.trevin-lee/cobrowser |
|---|---|---|
| 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 | Not known |
| Needs first | Node.js | – |
| Licence | APACHE-2.0 | MIT |
| Latest version | 1.10.1004 | 0.9.32 |
| 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 | No install config |
| Downloads last week | Not known | Not known |
| Install | Install Chrome DevTools MCP | Install Cobrowser |
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 Chrome DevTools MCP with othersCompare Cobrowser with others