Browserless MCP MCP Server

MCP (Model Context Protocol) server for the Browserless.io browser automation platform. The browserless mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 12 defined tools rather than through you.

What it actually does

MCP (Model Context Protocol) server for Browserless.io — expose the Browserless smart scraper API to LLM clients like Claude Desktop, Cursor, VS Code, and Windsurf.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• browserless_smartscraper — Scrape a single webpage and return its content as markdown or HTML. Handles JavaScript-heavy pages and anti-bot measures automatically. For content
• browserless_search — Search the web using Browserless and optionally scrape each result. Supports web, news, and image search with geo-targeting and time filters
• browserless_map — Discover and map all URLs on a website. Scans via sitemaps and link extraction. Returns URLs with optional titles and descriptions. Useful for site
• browserless_crawl — Crawl a website and scrape every discovered page. Supports depth control, path filtering, sitemap strategies, and configurable scrape options
• browserless_performance — Run Lighthouse audits on any URL. Returns scores and metrics for accessibility, best practices, performance, PWA, and SEO. Optionally filter by
• browserless_function — Execute custom Puppeteer JavaScript on the Browserless cloud. The function receives a page object and optional context; return { data, type } to
• browserless_export — Export a webpage via the Browserless /export API. Fetches the URL and returns its native content (HTML, PDF, image, etc.) with automatic content-type
• browserless_agent — Drive a persistent browser session via a ReAct loop: snapshot the page, plan, batch interactions (click, type, scroll, evaluate, etc.), and
• browserless_skill — Load an on-demand recipe for a non-trivial page mechanic (shadow DOM, cookie consent, modals, captchas, dynamic content, snapshot misses
• Cursor — The Cursor tool exposed by this server
• Windsurf — The Windsurf tool exposed by this server
• Tests — Tests run automatically on every pull request via the Test workflow on Node 24. PRs must keep the suite green before

Configuration

You will need 3 environment variables: BROWSERLESS_TOKEN, BROWSERLESS_API_URL, AMPLITUDE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Browserless MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the browserless mcp mcp server does with a few real requests.

When to reach for it

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Browserless MCP's toolset — browserless_smartscraper, browserless_search, browserless_map and 9 more — is a fair guide to whether it matches your workflow. It is maintained by browserless; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.