Generated 7/5/2026, 6:58:49 PM
Firecrawl Repo Map: What To Open, What To Use, What To Avoid
This page does not launch anything. It explains what each downloaded repo appears to do before you open it, with a Firecrawl-heavy priority lane for scraping, crawling, HTML-to-markdown, graphing, agents, SDKs, and plugins.
101All local Firecrawl clones
57P0/P1/P2 items worth keeping visible
66Your highest-value topic area
59Likely .env/API setup before testing
0Resolve install/toolchain first
Firecrawl-First Queue
This includes apps and non-app components because you said Firecrawl, scraping, HTML, graphs, and stored Firecrawl workflows matter most.
57 useful components tagged
Key rule before opening
Assume a Firecrawl API key for serious use. The MCP server has a limited keyless hosted mode for scrape/search/interact, but crawl, map, agent, extract, and higher-volume work need a key. Extra products like OpenAI, Anthropic, Supabase, Clerk, Stripe, Convex, or email services are called out per repo.
Readiness Mix
How the 101 repos break down before opening anything.
Most Common Key Providers
Detected from README and .env examples.
Scraping, HTML, And Graph Targets
The repos most aligned to scraping/crawling, HTML cleanup, markdown conversion, and visualizing data.
Scrape / Crawl
HTML / Markdown
Graphs / Data Viz
Recommended First Opens
Best candidates to choose from first. Some still need keys, but dependencies are mostly ready.
Do Not Open Yet
These are blocked by installs, missing toolchains, or are not app surfaces.
All Firecrawl Repositories
Search and filter everything downloaded locally.
visible
| Repository / What It Does | Focus | Decision | Keys Needed | Run/Test Command | Before Opening |
|---|