MCP servers · cloudcorprecords

crawlport: Firecrawl web data for agents, as CLI or MCP server

A Firecrawl-backed tool, usable as a CLI or stdio MCP server, that gives agents scraping, mapping, crawling, search, extraction, research and llms.txt generation for web content.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

crawlport gives an agent access to the readable web through Firecrawl. A single page comes back as clean markdown. For a whole site it can map discovered pages, crawl a section, or scrape a list of URLs in batch. For a question it can run a web search, extract structured fields from pages into a schema the user describes, research across many sources, or draft the llms.txt file a site would publish about itself.

It suits work where web content needs to become text or structured data for later steps, without handling page fetching directly. It runs as a command-line tool or as a stdio MCP server exposing ten tools: scrape, map, search, crawl, crawl status, extract, batch scrape, batch status, deep research and llms.txt generation. Optional arguments are passed on only when set, so the API's defaults apply otherwise.

Setup requires a Firecrawl API key, exported as an environment variable. Crawl and batch jobs are asynchronous: the start call returns a job id, and a matching status call reads progress and results. Successful CLI calls print the API's JSON response, and tool results are the upstream JSON. The project is released under the MIT license.

Limitations and requirements

Requires a Firecrawl API key set in the FIRECRAWL_API_KEY environment variable; without it every command and tool call fails and nothing is sent. Crawl and batch jobs run asynchronously and must be polled with status calls to get results.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CloudCorpRecords/crawlport

    Firecrawl web data: scrape, map, search, crawl, extract, research, and llms.txt.

    v0.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
neondatabase

Neon MCP Server (Postgres)

Neon's MCP server for managing Neon Postgres in plain language: create projects and branches, run queries and prepare schema migrations from your editor.

663 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
supabase-community

Supabase MCP Server

Supabase's MCP server that connects an AI assistant to your Supabase project to design tables, run queries, read configuration and look up documentation.

Data & databasesSoftware development
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
modelcontextprotocol

MCP reference servers

Seven small example servers maintained by the Model Context Protocol project: files, Git, web fetching, memory, time, step-by-step thinking and a test server.

92K GitHub starsSoftware development
Updated 17 Nov 2026