Ext Ops Panel
Open dashboard
Comparison

Firecrawl vs mcp-my-site

Firecrawl is an MCP server published by firecrawl. Marketplaces we read that list it: 1 (Docker MCP Catalog). mcp-my-site is an MCP server published by pournasserian. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
MarketplaceFirecrawlmcp-my-site
Docker MCP Catalog Listed
Version: sha256:28e677a10704
Forks (GitHub): 917
Pulls (Docker Hub): 142 683
Stars (Docker Hub): 20
Stars (GitHub): 7 676
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.0
Forks (GitHub): 1
Stars (GitHub): 5
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 mcp-my-site
FactFirecrawlmcp-my-site
Marketplaces that list it11
Stars (GitHub) (differs)7 676 (better)5 (worse)
Pulls (Docker Hub) (differs)142 683No figure on Docker Hub
Forks (GitHub) (differs)917 (better)1 (worse)
Last release (differs)Not published2026-10-24
Where it runs (differs)On your machine (mcp/firecrawl)Remote server (ai.pournasserian.com/mcp)
Transport (differs)stdioStreamable HTTP
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/pournasserian/mcp-my-site
Changes in the last 7 days (differs)14
First seen (differs)2026-10-112026-10-17
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 302 (36 h ago)

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.

mcp-my-site

In its own words, on Official MCP Registry:

Search and fetch tools for one website, served from an index you build with the mcpmysite crawler.

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)

mcp-my-site As a remote MCP server

Claude Code
claude mcp add --transport http mcp-my-site https://ai.pournasserian.com/mcp

Requires: AI_API_KEY (secret), Index__Path

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

Only mcp-my-site has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of mcp-my-site 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 mcp-my-site asks for

  • AI_API_KEY (secret)
  • Index__Path

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

What it can do: Firecrawl · What it can do: mcp-my-site · 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