Firecrawl vs io.github.CumulativeWebInc/cwi-discovery-engine
Firecrawl is an MCP server published by firecrawl. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.CumulativeWebInc/cwi-discovery-engine is an MCP server published by CumulativeWebInc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 |  Firecrawl |  io.github.CumulativeWebInc/cwi-discovery-engine |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:28e677a10704 Forks (GitHub): 928 Pulls (Docker Hub): 140 854 Stars (Docker Hub): 20 Stars (GitHub): 7 647 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.3.0 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | Firecrawl | io.github.CumulativeWebInc/cwi-discovery-engine |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 7 647 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 140 854 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 928 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | On your machine (mcp/firecrawl) | Remote server (cwi-machine-data.hp-ace.workers.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 26 | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/mendableai/firecrawl-mcp-server | github.com/cumulativewebinc/cwi-learn |
| Changes in the last 7 days (differs) | 1 | 5 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days 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
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.
io.github.CumulativeWebInc/cwi-discovery-engine
CWI Discovery Engine: 29-tool music catalog MCP — search, sync, Radio 365 live, chaining.
How to run each
Firecrawl As a local MCP server: Docker image
claude mcp add --env "FIRECRAWL_API_KEY=<YOUR_FIRECRAWL_API_KEY>" --transport stdio firecrawl -- docker run -i --rm -e FIRECRAWL_API_KEY mcp/firecrawlRequires: FIRECRAWL_API_KEY (secret)
io.github.CumulativeWebInc/cwi-discovery-engine As a remote MCP server
claude mcp add --transport http cwi-discovery-engine https://cwi-machine-data.hp-ace.workers.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.CumulativeWebInc/cwi-discovery-engine has a remote endpoint we check. How we check endpoints
Tools each declares
Only Firecrawl has
firecrawl_agentfirecrawl_agent_statusfirecrawl_check_crawl_statusfirecrawl_crawlfirecrawl_extractfirecrawl_feedbackfirecrawl_interactfirecrawl_interact_stopfirecrawl_mapfirecrawl_monitor_checkfirecrawl_monitor_checksfirecrawl_monitor_create
Show the remaining 14
firecrawl_monitor_deletefirecrawl_monitor_getfirecrawl_monitor_listfirecrawl_monitor_runfirecrawl_monitor_updatefirecrawl_parsefirecrawl_research_inspect_paperfirecrawl_research_read_paperfirecrawl_research_related_papersfirecrawl_research_search_githubfirecrawl_research_search_papersfirecrawl_scrapefirecrawl_searchfirecrawl_search_feedback
Only io.github.CumulativeWebInc/cwi-discovery-engine has
find_tracks_for_briefget_announcementsget_artistget_eventsget_featuredget_genreget_graphget_labelget_lyricsget_playlistsget_press_kitget_radio
Show the remaining 17
get_recommendationsget_releaseget_requestsget_scheduleget_sync_catalogget_trackget_up_nextget_videosnominate_featuredpitch_for_playlistrequest_songrsvpsearch_catalogsemantic_searchsubmit_for_airplaysubmit_sync_briefsync_search
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.CumulativeWebInc/cwi-discovery-engine as of 2026-10-16). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of io.github.CumulativeWebInc/cwi-discovery-engine publish no settings it asks for, so we do not compare settings.
What it can do: Firecrawl · What it can do: io.github.CumulativeWebInc/cwi-discovery-engine · 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.