Firecrawl Workflows vs Brasspage Apify Actors
Firecrawl Workflows is a plugin bundle for AI coding tools published by Firecrawl. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Brasspage Apify Actors is an MCP server published by brasspage.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 Workflows |  Brasspage Apify Actors |
|---|---|---|
| Community marketplace firecrawl/firecrawl-workflows | Listed Version: 0.1.0 Forks (GitHub): 44 Stars (GitHub): 219 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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 Workflows | Brasspage Apify Actors |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 219 | No figure on GitHub |
| Forks (GitHub) (differs) | 44 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.apify.com) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 16 | Not a bundle |
| Licence (differs) | ISC | Not stated |
| Repository (differs) | github.com/firecrawl/firecrawl-workflows | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-18 | 2026-10-22 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded less than an hour ago, requires authentication |
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 Workflows
Outcome-focused Firecrawl workflow skills for research, SEO audits, QA, knowledge bases, lead lists, dashboard reporting, shopping, and design-system extraction.
Brasspage Apify Actors
Six AI-built Apify Actors: ATS jobs, PDF OCR, Lighthouse audits, transcripts, Sheets, site audits
How to run each
Firecrawl Workflows As a Claude Code plugin
/plugin marketplace add firecrawl/firecrawl-workflows
/plugin install firecrawl-workflows@firecrawl-workflowsBrasspage Apify Actors
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Brasspage Apify Actors has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Firecrawl Workflows · What it can do: Brasspage Apify Actors · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.