tabbied-mcp vs Firecrawl MCP Server
tabbied-mcp is an MCP server published by tabbied-design. Marketplaces we read that list it: 1 (npm registry (MCP servers)). 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). As of our marketplace pass on 2026-11-11. 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 |  tabbied-mcp |  Firecrawl MCP Server |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 0.3.2 Downloads/month (npm): 917 Downloads/week (npm): 136 Forks (GitHub): 1 Stars (GitHub): 10 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.39.0 Downloads/month (npm): 517 013 Downloads/week (npm): 158 613 Forks (GitHub): 929 Stars (GitHub): 7 801 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:3b22a74af198 Forks (GitHub): 929 Pulls (Docker Hub): 150 055 Stars (Docker Hub): 20 Stars (GitHub): 7 801 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 | tabbied-mcp | Firecrawl MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 10 (worse) | 7 801 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 150 055 |
| Forks (GitHub) (differs) | 1 (worse) | 929 (better) |
| Last release (differs) | 2026-10-18 (worse) | 2026-11-10 (better) |
| Where it runs (differs) | On your machine (tabbied-mcp) | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 28 |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 18 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/tabbied-design/tabbied | github.com/firecrawl/firecrawl-mcp-server |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 17 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
tabbied-mcp
MCP server for Tabbied: search, look at, and render its generative pattern designs from any MCP client.
Firecrawl MCP Server
Firecrawl, the context API for AI agents: search, scrape, interact with the web, plus paper search.
How to run each
tabbied-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Firecrawl MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of tabbied-mcp publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of tabbied-mcp publish no settings it asks for, so we do not compare settings.
What it can do: tabbied-mcp · What it can do: Firecrawl MCP Server · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). 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.