Ext Ops Panel
Open dashboard
Comparison

llm-council-plugin vs io.github.HarimxChoi/google-surf-mcp

llm-council-plugin is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑01.

llm-council-plugin is a plugin bundle for AI coding tools published by xrf9268-hue. No marketplace we read lists it any more. 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-11-07. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacellm-council-pluginio.github.HarimxChoi/google-surf-mcp
Community marketplace hey-yvan/llm-council-plugin Removed on 2026-11-01
Version: 1.0.0
Forks (GitHub): 9
Stars (GitHub): 20
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.6
Downloads/month (npm): 1 249
Downloads/week (npm): 613
Forks (GitHub): 32
Stars (GitHub): 291
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.1.6
Downloads/month (npm): 1 249
Downloads/week (npm): 613
Forks (GitHub): 32
Stars (GitHub): 291
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

llm-council-plugin vs io.github.HarimxChoi/google-surf-mcp
Factllm-council-pluginno longer listed · io.github.HarimxChoi/google-surf-mcp
Marketplaces that list it (differs)02
Stars (GitHub) (differs)20291
Forks (GitHub) (differs)932
Last release (differs)Not published2026-11-07
Where it runs (differs)Installs as a plugin bundleOn your machine (google-surf-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published29, secrets among them: 4
Hooks it runs (differs)6Not published
Parts of the bundle (differs)11Not a bundle
LicenceMITMIT
Repository (differs)github.com/xrf9268-hue/llm-council-plugingithub.com/harimxchoi/google-surf-mcp
Changes in the last 7 days22
First seen (differs)2026-10-202026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of llm-council-plugin

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • multi-ai-consultant

    Consult external AIs (Gemini 2.5 Pro, OpenAI Codex, Claude) for second opinions. Use for debugging failures, architectural decisions, security validation, or need fresh…

    by Claude Skills Maintainers · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • consultant

    Flexible multi-provider LLM consultations using Python/LiteLLM - includes consultant agent, review/bug-investigation commands, and consultant skill for deep AI-powered code…

    by doodledood · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • second-opinion

    Get a second opinion from the OpenAI (Codex), Google (Antigravity CLI, agy) or Anthropic (Claude Code) CLIs. Single provider, multi-round consultation, diff review, or multi-model…

    by Petr Simecek · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Orchestrator

    Let one coding-agent CLI consult another: Codex, Claude Code, OpenCode, Copilot or Antigravity.

    by crAK1644 · MCP server

    Listed on: Official MCP Registry, PyPI (MCP servers) · Describes nearly the same job

  • codex-advisor

    Get a second opinion from GPT-6 Astra via Codex CLI before big decisions.

    by Fatih C. Akyon · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • thread-keeper

    Multi-agent shared brain across Claude, Codex, Antigravity, Gemini, Copilot, and VS Code.

    by po4erk91 · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

llm-council-plugin

In its own words, on Community GitHub marketplaces:

Multi-model consensus engine that summons OpenAI Codex, Google Gemini, and Claude to collaboratively answer your technical questions through peer review and synthesis.

io.github.HarimxChoi/google-surf-mcp

In its own words, on Official MCP Registry:

Web, academic and code search with graph RAG, data lineage, ontology and cross-project schema links.

How to run each

llm-council-plugin

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.HarimxChoi/google-surf-mcp As a local MCP server: npm package

Claude Code
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-mcp

Requires: 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

The marketplaces of llm-council-plugin publish no settings it asks for, so we do not compare settings.

What it can do: llm-council-plugin · 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.

Where the data comes from: how the catalog is built