Ext Ops Panel
Open dashboard
Comparison

Firecrawl vs Zoteus

Firecrawl is an MCP server published by firecrawl. Marketplaces we read that list it: 1 (Docker MCP Catalog). Zoteus is an MCP server published by oscardvs. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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

Where each is published
MarketplaceFirecrawlZoteus
Docker MCP Catalog Listed
Version: sha256:28e677a10704
Forks (GitHub): 905
Pulls (Docker Hub): 137 995
Stars (Docker Hub): 20
Stars (GitHub): 7 596
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.22.4
Downloads/month (npm): 6 515
Downloads/week (npm): 371
Forks (GitHub): 5
Stars (GitHub): 58
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

Firecrawl vs Zoteus
FactFirecrawlZoteus
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)7 596 (better)58 (worse)
Pulls (Docker Hub) (differs)137 995No figure on Docker Hub
Forks (GitHub) (differs)905 (better)5 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/firecrawl)Remote server or your machine
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)26Not published
Environment variables it asks for (differs)8, secrets among them: 13, secrets among them: 1
Parts of the bundle (differs)Not a bundle5
LicenceMITMIT
Repository (differs)github.com/mendableai/firecrawl-mcp-servergithub.com/oscardvs/zoteus
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 22 h ago, requires a key

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

Firecrawl

In its own words, on Docker MCP Catalog:

🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.

Zoteus

In its own words, on Official MCP Registry:

Zotero MCP server for Claude and ChatGPT: search, citations, safe writes, PDF passages and pages.

How to run each

Firecrawl As a local MCP server: Docker image

Claude Code
claude mcp add --env "FIRECRAWL_API_KEY=<YOUR_FIRECRAWL_API_KEY>" --transport stdio firecrawl -- docker run -i --rm -e FIRECRAWL_API_KEY mcp/firecrawl

Requires: FIRECRAWL_API_KEY (secret)

Zoteus As a remote MCP server

Claude Code
claude mcp add --transport http zoteus https://mcp.zoteus.com/mcp

Requires: ZOTERO_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Zoteus has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Zoteus publish no list of tools, so we do not compare tools.

Settings each asks for

Only Firecrawl asks for

  • FIRECRAWL_API_KEY (secret)
  • FIRECRAWL_API_URL
  • FIRECRAWL_CREDIT_CRITICAL_THRESHOLD
  • FIRECRAWL_CREDIT_WARNING_THRESHOLD
  • FIRECRAWL_RETRY_BACKOFF_FACTOR
  • FIRECRAWL_RETRY_INITIAL_DELAY
  • FIRECRAWL_RETRY_MAX_ATTEMPTS
  • FIRECRAWL_RETRY_MAX_DELAY

Only Zoteus asks for

  • ZOTERO_API_KEY (secret)
  • ZOTEUS_ALLOW_DELETE
  • ZOTEUS_LOCAL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Firecrawl · What it can do: Zoteus · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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