Ext Ops Panel
Open dashboard
Comparison

Firecrawl vs XERJ

Firecrawl is an MCP server published by firecrawl. Marketplaces we read that list it: 1 (Docker MCP Catalog). XERJ is an MCP server published by xerj-org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceFirecrawlXERJ
Docker MCP Catalog Listed
Version: sha256:28e677a10704
Forks (GitHub): 919
Pulls (Docker Hub): 143 082
Stars (Docker Hub): 20
Stars (GitHub): 7 685
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0-rc.99
Forks (GitHub): 1 137
Stars (GitHub): 15 561
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 XERJ
FactFirecrawlXERJ
Marketplaces that list it11
Stars (GitHub) (differs)7 685 (worse)15 561 (better)
Pulls (Docker Hub) (differs)143 082No figure on Docker Hub
Forks (GitHub) (differs)919 (worse)1 137 (better)
Last release (differs)Not published2026-10-26
Where it runs (differs)On your machine (mcp/firecrawl)On your machine (https://github.com/xerj-org/xerj/releases/download/mcpb-v1.0.0-rc.99/xerj-mcp-1.0.0-rc.99.mcpb)
Transportstdiostdio
Tools it declares (differs)26Not published
Environment variables it asks for (differs)8, secrets among them: 12, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/mendableai/firecrawl-mcp-servergithub.com/xerj-org/xerj
Changes in the last 7 days (differs)14
First seen (differs)2026-10-112026-10-24

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, the context API for AI agents: search, scrape, and interact with the web, plus parse, crawl, map, Agent and Monitor, from any MCP client.

XERJ

In its own words, on Official MCP Registry:

The search engine for AI agents: cited answers from your local code, docs, specs and logs.

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)

XERJ

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

Requires: XERJ_AUTH (secret)

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

Tools each declares

The marketplaces of XERJ 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 XERJ asks for

  • XERJ_AUTH (secret)
  • XERJ_URL

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

What it can do: Firecrawl · What it can do: XERJ · 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. 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