Skip to main content
Learn how to use Firecrawl’s core features to scrape GitHub repositories, issues, and documentation.
There are two ways to get GitHub data with Firecrawl. You can scrape, map, or crawl a specific github.com URL (what the rest of this page covers), or you can use the Research Index GitHub search to semantically discover relevant issues, pull requests, discussions, and READMEs across GitHub without knowing the exact URL.

Setup

Scrape with JSON Mode

Extract structured data from repositories using Zod schemas.
Find repositories, issues, or documentation on GitHub.

Search GitHub with the Research Index

Firecrawl’s Research Index includes a GitHub index that semantically searches indexed public GitHub issues, pull requests, discussions, and repository READMEs. It’s useful for finding implementation details and engineering prior art when you don’t know the exact repository or URL.
You can also reach the same GitHub index via the general /search endpoint with the github category.
See the Research Index guide for Python, cURL, CLI, and MCP usage.

Scrape

Scrape a single GitHub page - repository, issue, or file.

Map

Discover all available URLs in a repository or documentation site. Note: Map returns URLs only, without content.

Crawl

Crawl multiple pages from a repository or documentation.

Batch Scrape

Scrape multiple GitHub URLs simultaneously.

Batch Scrape with JSON Mode

Extract structured data from multiple repositories at once.