Browser Use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Description from the maker (original English)
Firecrawl web data: scrape, map, search, crawl, extract, research, and llms.txt.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"crawlport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/crawlport",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add crawlport -- npx -y @reneturcios/crawlport mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"crawlport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/crawlport",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"crawlport": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/crawlport",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 6 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
MCP server for browser use access
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
crawlport is a doorway between an agent and the readable web, backed by Firecrawl. Give it one page and it hands back clean markdown; give it a whole site and it will map the pages, crawl a section, or scrape a list in batch; give it a question and it can search, pull structured fields out of pages to a schema you describe, research across many sources, or draft the llms.txt a site would publish about itself. It runs as a CLI or as an MCP server, and it needs a Firecrawl API key.
Get a key from Firecrawl and export it:
export FIRECRAWL_API_KEY=<redacted>
Without the variable set, every command and tool call fails with an error that names FIRECRAWL_API_KEY — nothing is sent anywhere.
npx @reneturcios/crawlport scrape https://example.com/some/page
Or run the container image:
docker run -i -e FIRECRAWL_API_KEY ghcr.io/cloudcorprecords/crawlport
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
# One page, as markdown (add --formats html,links etc. for more)
crawlport scrape https://example.com/article --only-main-content
crawlport map https://example.com --search pricing --limit 100
crawlport search "standing desk reviews" --limit 5 --lang en --country US
crawlport crawl https://example.com/docs --limit 50 --max-depth 2 crawlport crawl-status
crawlport extract https://example.com/a https://example.com/b --prompt "pull the price" crawlport batch-scrape https://example.com/a https://example.com/b crawlport batch-status
crawlport deep-research "home battery storage costs in 2026" --max-urls 40 crawlport llmstxt https://example.com --max-urls 25
crawlport --version
Successful calls print the API's JSON response. Crawl and batch jobs are asynchronous upstream: the start call returns a job id, and the matching status command reads its progress and results. Exit codes: 0 on success, 1 when the API call fails (including a missing key), 2 for usage errors.
One bin serves both faces. The mcp subcommand starts a stdio MCP server:
npx -y @reneturcios/crawlport mcp
MCP client configuration:
{
"mcpServers": { "crawlport": { "command": "npx", "args": ["-y", "@reneturcios/crawlport", "mcp"], "env": { "FIRECRAWL_API_KEY": "your-key-here" } } } }
| Tool | Input | What it does |
|---|---|---|
firecrawl_scrape | url (required); formats, onlyMainContent, waitFor, timeout, actions, includeTags, excludeTags, blockAds, proxy (optional) | Scrape one page via POST /v1/scrape. |
firecrawl_map | url (required); search, limit, ignoreSitemap | List a site's discovered URLs via POST /v1/map. |
firecrawl_search | query (required); limit, lang, country, scrapeOptions | Web search via POST /v1/search, optionally scraping each result. |
firecrawl_crawl | url (required); limit, maxDepth, allowBackwardLinks, allowExternalLinks, excludePaths, includePaths, scrapeOptions | Start a crawl via POST /v1/crawl; returns a job id. |
firecrawl_check_crawl_status | id (required) | Poll a crawl job via GET /v1/crawl/{id}. |
firecrawl_extract | urls (required); prompt, schema, enableWebSearch, allowExternalLinks | LLM extraction to a prompt/schema via POST /v1/extract. |
firecrawl_batch_scrape | urls (required); formats, onlyMainContent | Start a batch scrape via POST /v1/batch/scrape; returns a job id. |
firecrawl_check_batch_status | id (required) | Poll a batch job via GET /v1/batch/scrape/{id}. |
firecrawl_deep_research | query (required); maxDepth, timeLimit, maxUrls | Multi-source research via POST /v1/deep-research. |
firecrawl_generate_llmstxt | url (required); maxUrls, showFullText | Generate llms.txt content via POST /v1/llmstxt. |
Tool results are the upstream JSON, pretty-printed as text. Optional arguments are forwarded only when provided, so the API's defaults apply otherwise. Upstream failures come back as tool errors carrying the HTTP status and the API's own message.
npm install
npm run build # tsc -> dist/ npm test # node test runner over test/*.test.ts, no network (fake fetch fixtures) npm run dev # run the CLI from source via tsx
MIT — see LICENSE.