io.github.Dayananda-D/devcdp vs io.github.NeoDrew/chromeflow
io.github.Dayananda-D/devcdp is an MCP server published by Dayananda-D. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.NeoDrew/chromeflow is an MCP server published by NeoDrew. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  io.github.Dayananda-D/devcdp |  io.github.NeoDrew/chromeflow |
|---|---|---|
| Official MCP Registry | Listed Version: 5.0.1 Downloads/month (npm): 221 Downloads/week (npm): 40 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 0.9.5 Forks (GitHub): 0 Stars (GitHub): 3 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 | io.github.Dayananda-D/devcdp | io.github.NeoDrew/chromeflow |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (worse) | 3 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (devcdp) | Not stated |
| Transport (differs) | stdio | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dayananda-d/devcdp | github.com/neodrew/chromeflow |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 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
io.github.Dayananda-D/devcdp
Chrome DevTools for AI assistants: console, network, DOM, source maps, breakpoints, live variables.
io.github.NeoDrew/chromeflow
Lets Claude Code or Codex CLI drive your real Chrome — sessions intact, 28 browser tools.
How to run each
io.github.Dayananda-D/devcdp As a local MCP server: npm package
claude mcp add --transport stdio devcdp -- npx -y devcdpio.github.NeoDrew/chromeflow
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands 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
The marketplaces of io.github.NeoDrew/chromeflow publish no settings it asks for, so we do not compare settings.
What it can do: io.github.Dayananda-D/devcdp · What it can do: io.github.NeoDrew/chromeflow · Compare two other plugins
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.