dev-loop vs io.github.HarimxChoi/google-surf-mcp
dev-loop is a plugin bundle for AI coding tools published by choiyounggi. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.HarimxChoi/google-surf-mcp is an MCP server published by HarimxChoi. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-21. 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 |   dev-loop |  io.github.HarimxChoi/google-surf-mcp |
|---|---|---|
| Community marketplace davepoon/buildwithclaude | Listed Version: 1.33.0 Forks (GitHub): 1 Stars (GitHub): 6 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.4 Downloads/month (npm): 1 729 Downloads/week (npm): 104 Forks (GitHub): 33 Stars (GitHub): 290 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.1.4 Downloads/month (npm): 1 729 Downloads/week (npm): 104 Forks (GitHub): 33 Stars (GitHub): 290 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 | dev-loop | io.github.HarimxChoi/google-surf-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 6 (worse) | 290 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 33 (better) |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (google-surf-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 29, secrets among them: 4 |
| Hooks it runs (differs) | 13 | Not published |
| Parts of the bundle (differs) | 27 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/choiyounggi/dev-loop | github.com/harimxchoi/google-surf-mcp |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-15 | 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
dev-loop
Multi-agent orchestration grounded in an LLM wiki. /dev-loop:orchestrate splits one goal into a dependency graph of parallel Claude Code sessions, each in its own worktree, and supervises them natively on Orca (a tracked Task + Dispatch per phase, pushed worker_done / question / escalation events instead of polling, stall detection; raw tmux fallback). Every plan decision must cite a page in a bundled best-practice wiki of 400+ pages across 10 domains, checked by machine gates and a fresh-context plan reviewer. Insights from your sessions are queued and turned into reviewed wiki PRs when you run /dev-loop:knowledge-flush (automatic flushing is opt-in and never bypasses permission checks).
io.github.HarimxChoi/google-surf-mcp
Web, academic and code search with graph RAG, data lineage, ontology and cross-project schema links.
How to run each
dev-loop As a Claude Code plugin
/plugin marketplace add davepoon/buildwithclaude
/plugin install dev-loop@buildwithclaudeio.github.HarimxChoi/google-surf-mcp As a local MCP server: npm package
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --env "ORCAROUTER_API_KEY=<YOUR_ORCAROUTER_API_KEY>" --env "SEARCH_API=<YOUR_SEARCH_API>" --transport stdio google-surf-mcp -- npx -y google-surf-mcpRequires: ANTHROPIC_API_KEY (secret), GITHUB_TOKEN (secret), ORCAROUTER_API_KEY (secret), SEARCH_API (secret)
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
Only dev-loop asks for
DEV_LOOP_WIKI_EMBED_MODELDEV_LOOP_WIKI_INDEXDEV_LOOP_WIKI_INDEX_DIR
Only io.github.HarimxChoi/google-surf-mcp asks for
ANTHROPIC_API_KEY (secret)CHROME_PATHGITHUB_TOKEN (secret)ORCAROUTER_API_KEY (secret)SEARCH_API (secret)SURF_ALLOW_PRIVATESURF_BROWSER_ENGINESURF_HEADLESSSURF_IDLE_CLOSE_MSSURF_LLM_HEALSURF_LLM_MODELSURF_LLM_PROVIDER
Show the remaining 17
SURF_LOCALESURF_PROFILE_ROOTSURF_RESEARCHSURF_RESEARCH_BROKER_IDLE_MSSURF_RESEARCH_QUERY_TIMEOUT_MSSURF_RESEARCH_READ_CONCURRENCYSURF_RESEARCH_REPO_AUTOSURF_RESEARCH_REPO_AUTO_MAX_FILESSURF_RESEARCH_REPO_AUTO_MAX_MBSURF_RESEARCH_ROOTSURF_RESEARCH_VECTOR_LOW_MEMORYSURF_RESEARCH_VECTOR_MODELSURF_RESEARCH_VECTOR_THREADSSURF_RETRIEVAL_MODESURF_SCHOLAR_PROVIDERSURF_SEARCH_PROVIDERSURF_TZ
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: dev-loop · What it can do: io.github.HarimxChoi/google-surf-mcp · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.