Firecrawl MCP Server vs Nicelydone
Firecrawl MCP Server is an MCP server published by firecrawl. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). Nicelydone is an MCP server published by nicelydoneapp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 3.38.0 Downloads/month (npm): 517 013 Downloads/week (npm): 158 613 Forks (GitHub): 927 Stars (GitHub): 7 779 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:3b22a74af198 Forks (GitHub): 927 Pulls (Docker Hub): 148 864 Stars (Docker Hub): 20 Stars (GitHub): 7 779 Not marked · First seen |
Not listed |
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
| Fact | Firecrawl MCP Server | Nicelydone |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 7 779 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 148 864 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 927 | No figure on GitHub |
| Last release (differs) | 2026-11-06 | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (mcp.nicelydone.club/mcp) |
| Transport (differs) | Streamable HTTP, stdio | Streamable HTTP |
| Tools it declares (differs) | 28 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 18 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/firecrawl/firecrawl-mcp-server | Not stated |
| Changes in the last 7 days (differs) | 9 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-27 |
| Endpoint at the last check (differs) | Responded 11 h ago | Status out of date: last check 42 h ago returned HTTP 401 |
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 MCP Server
Firecrawl, the context API for AI agents: search, scrape, interact with the web, plus paper search.
Nicelydone
Search real web app screens, UI elements, and user flows. Requires Premium access and OAuth.
How to run each
Firecrawl MCP Server As a remote MCP server
claude mcp add --transport http firecrawl-mcp-server https://mcp.firecrawl.dev/v2/mcp --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: FIRECRAWL_API_KEY (secret), Authorization header
Nicelydone As a remote MCP server
claude mcp add --transport http nicelydone https://mcp.nicelydone.club/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
The marketplaces of Nicelydone publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Nicelydone publish no settings it asks for, so we do not compare settings.
What it can do: Firecrawl MCP Server · What it can do: Nicelydone · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.