firecrawl-developer-search
firecrawl developer search
Via the Firecrawl MCP (preferred)
This plugin bundles the Firecrawl MCP server. When it's connected, prefer the native firecrawl_developer_search tool over the CLI — it needs no local install and authenticates through the plugin's one-time browser sign-in. The firecrawl CLI commands below are the fallback for when the MCP isn't connected.
Semantic search over indexed developer sources. Each result carries an id, a url, a title, and the matched passages in markdown, so tables and code blocks survive intact.
The id prefix tells you what kind of source a hit is: doc:, issue:, pull_request:, or readme:.
When to use
- The question is about code behaviour, a library or framework, an API contract, an error message, or a known bug
- You want the issue that reported it, the merged PR that fixed it, or the doc page that defines the contract — not a blog post describing it
- Before falling back to a general web search: reach for the index first, the open web second
Not for this skill: comparisons and opinions ("X vs Y"), news and outages, or a project with no public repo or indexed docs. Those are firecrawl-search plus firecrawl-scrape questions.