pickfit

BrowseMCP servers

Firecrawl MCP Server

MCP server that lets AI clients search, scrape, crawl, map and interact with web pages via the Firecrawl API, returning Markdown or structured data.

Use it

Before you install: known vulnerabilities

pickfit found 1 known high or critical vulnerability in the packages a fresh install brings (OSV.dev, 16 Nov 2026). Weigh this before you install it.

  • npm:zod 3.25.76 Zod can exhaust memory while validating oversized constrained collections (GHSA-mrhx-c7xc-m3w5, high, fixed in 4.6.6)

Linux x86_64

You need first

  • Needs the network
  • Keys or accounts: Firecrawl API key
  1. npm install -g firecrawl-mcp

    npm install -g firecrawl-mcp

Add it to your agent

claude mcp add firecrawl-mcp-server -e FIRECRAWL_API_KEY='<FIRECRAWL_API_KEY>' -- firecrawl-mcp
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "firecrawl-mcp-server": {
      "command": "firecrawl-mcp",
      "args": [],
      "env": {
        "FIRECRAWL_API_KEY": "<FIRECRAWL_API_KEY>"
      }
    }
  }
}

You fill in

  • FIRECRAWL_API_KEY: Firecrawl API key for cloud API (required)

Ask the user for FIRECRAWL_API_KEY; pickfit never had a value, so these are placeholders.

Add firecrawl-mcp as an MCP server in your AI client, and its Firecrawl tools such as firecrawl_scrape and firecrawl_search become available.

What it does

  • Search the web and optionally get page content
    Not tested
  • Scrape any URL into Markdown
    Not tested
  • Crawl or map a website
    Not tested
  • Interact with pages in a real browser
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 0 of 4 features work
  4. Works offline

Good for

  • scrape a known URL into Markdown
  • discover all URLs on a website
  • monitor a page for content changes
  • parse PDFs and documents

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client connects and lists its tools

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026
  • Version 3.40.0

An MCP client handshake over stdio listed 28 tools.

Differences the test machine hit

  • README: FIRECRAWL_API_KEY is required
    In the test: The server starts and completes the MCP handshake (28 tools) without FIRECRAWL_API_KEY; the key is only needed for tool calls to the Firecrawl API

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.