Does firecrawl-mcp-server run?

Yes. firecrawl-mcp-server runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.

How did Argusic test firecrawl-mcp-server?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 089748bed688. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test firecrawl-mcp-server?

The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does firecrawl-mcp-server take to install?

3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.

Does firecrawl-mcp-server need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing firecrawl-mcp-server?

3 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for firecrawl-mcp-server?

All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

firecrawl-mcp-server

🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.

Runssource: GitHub homepageJavaScriptMITcommit 089748bed688

JavaScript, MIT licensed. The project labels itself: batch processing, claude, content extraction, data collection, firecrawl, firecrawl ai, javascript rendering and llm tools.

firecrawl-mcp-server runs. An Argusic agent installed it in 3 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.

Firecrawl MCP Server v3.24.1 builds, installs, and starts successfully with 25 tools in stdio mode; 81 of 84 tests pass.
What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 89.3 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 89.3 / 100
cost of the verifying run: $0.09 (measured)
recorded runs: 2
last tested: 2026-09-16
stars: 7,500
forks: 891
open issues: 145
watchers: 44
size: 4 MB
created: 2024-12-06
last push: 2026-09-22

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-22. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing firecrawl-mcp-server, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

Node.js v18 installed but project requires >=22; undici dependency crashes on Node 18 with 'File is not defined'2 minutes
Tests 34/59: keyless HTTP cloud tool listing returns all 25 tools instead of only parse/scrape/search
Test 70: firecrawl_extract deprecated response causing TypeError

Install time: 3 minutes
Cold machine to finish: 24 minutes
Errors hit and fixed: 3 hit, 1 fixed with no human help
Model tokens used: 177,909
Exact commit tested: 089748bed688
Container image: sha256:4c3d41857be3

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

How the result was proved: runs before 2026-09-07 did not record the command used to check the result
Peak GPU memory: this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run: each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- **final_state**: Build, install, and 25-tool MCP server work; tests pass 81/84.
tokens used
177,909
The server is fully operational with all 25 tools. Now I'll compute the result:
- **install_succeeded**: Yes
- **launch_succeeded**: Yes (server works in both stdio and HTTP modes, test suite runs)
- **install_minutes**: ~3 minutes (Node 22 download + npm install + test run)
- **errors**:
  1. Node.js 18 installed instead of required >=22 → Fix: download and use Node 22 binary
  2. 3 test failures due to codebase-test mismatch (keyless tool filtering removed, deprecated extr…
- **test_depth**: tier1_real (verified server starts and responds with all tools in stdio mode)
- **final_state**: Build, install, and 25-tool MCP server work; tests pass 81/84.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

Reached a running state on a clean machine, with the session recorded.
Installed in 3 minutes.
Ran without a GPU, so it does not need one to start.
Licensed MIT, as reported by its host.
Measured 2 times, so the result is not a one-off.

What did not, or is not known

Hit 3 errors during setup, 2 of which were not solved.

What it is a reasonable choice for

Trying it on a laptop or a small server: it reached a running state without a GPU.
A quick evaluation: it was running 3 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Runs with mocks	92.00	0.01	2026-09-16 05:22 UTC
Argusic Runner	2/3	Runs	86.67	0.09	2026-09-04 05:18 UTC

Topics (from GitHub)

batch-processing claude content-extraction data-collection firecrawl firecrawl-ai javascript-rendering llm-tools mcp mcp-server model-context-protocol search-api web-crawler web-scraping

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/firecrawl-mcp-server.svg)](https://argusic.com/subject/firecrawl-mcp-server)

Questions

Does firecrawl-mcp-server run?: Yes. firecrawl-mcp-server runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test firecrawl-mcp-server?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 089748bed688. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test firecrawl-mcp-server?: The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does firecrawl-mcp-server take to install?: 3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does firecrawl-mcp-server need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing firecrawl-mcp-server?: 3 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for firecrawl-mcp-server?: All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.