Ext Ops Panel
Open dashboard
Comparison

senior-fable vs io.github.HarimxChoi/google-surf-mcp

senior-fable is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑05.

senior-fable is a plugin bundle for AI coding tools published by Andy Shaman. 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-09. 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
Marketplacesenior-fableio.github.HarimxChoi/google-surf-mcp
Community marketplace andyshaman/senior-fable Removed on 2026-11-05
Version: 1.4.1
Forks (GitHub): 1
Stars (GitHub): 27
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

senior-fable vs io.github.HarimxChoi/google-surf-mcp
Factsenior-fableno longer listed · io.github.HarimxChoi/google-surf-mcp
Marketplaces that list it (differs)02
Stars (GitHub) (differs)27291
Forks (GitHub) (differs)132
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
Parts of the bundle (differs)5Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/andyshaman/senior-fablegithub.com/harimxchoi/google-surf-mcp
Changes in the last 7 days22
First seen (differs)2026-10-152026-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 senior-fable

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

  • guild

    Guild turns Claude Code into a self-evolving team of specialist agents for larger software tasks. It plans before execution, selects the right specialists, assembles focused…

    by lookatitude · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • coordinator-claude

    Engineering management layer for Claude Code --- structures your session like a real dev team where you're PM and Claude is EM. Provides session workflows, multi-persona code…

    by oduffy-delphi · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • orchestrator-supaconductor

    Conductor v3 — Multi-agent orchestration with Evaluate-Loop, parallel execution, Board of Directors, and bundled SupaConductor skills for Claude Code

    by Ibrahim · Plugin bundle

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

  • ai-team-os

    Shared task wall, memory, reports, channels and Dashboard for Claude Code and Codex; Claude Code plugin installation and an independent Codex adapter

    by CronusL-1141 · Plugin bundle

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

  • persona

    The user can inject experts into their Claude Code session. It provides the programmed experts with specific priorities, communication styles, and domain knowledge to help. Each…

    by tatertot365 · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • mexus-agent-team

    Standalone Markdown-only Agent Team plugin for Claude Code and Codex. Coordination happens through ordinary Markdown files in the current project: agent-team/ ├──…

    by yofine · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

senior-fable

In its own words, on Community GitHub marketplaces:

Turns your top-tier model into a tech lead: it keeps decomposition, architecture and final synthesis, routing work to a role roster — an implementer for feature-sized coding, a worker for mechanical edits, a read-only investigator for long digs, and an independent reviewer for finished work. Every role's model is overridable from CLAUDE.md.

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

senior-fable

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 senior-fable publish no settings it asks for, so we do not compare settings.

What it can do: senior-fable · 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