For AI agents: a documentation index is available at /llms.txt
Skip to main content

MCP

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and data sources. Browserless provides two MCP servers, each designed for a different use case.

Browserless MCP Server​

The primary MCP server for browser automation. Connect Claude Desktop, Cursor, VS Code, Windsurf, or any MCP-compatible client and give your AI assistant the ability to scrape pages, take screenshots, generate PDFs, download files, and run custom Puppeteer code — all powered by Browserless's managed, stealth-enabled browser infrastructure.

Use this when you need your AI to interact with the live web — scraping content, extracting data, exporting pages, or executing browser-side JavaScript.

Key capabilities:

  • Browser Agent — a stateful, snapshot-driven browser your AI can navigate and interact with across turns (logins, multi-step flows, form filling)
  • Smart Scraper — cascading scrape strategies (HTTP fetch, proxy, headless browser, CAPTCHA solving) selected automatically
  • Custom code execution — run arbitrary Puppeteer JavaScript on the Browserless cloud
  • File downloads — trigger and retrieve browser-initiated downloads
  • Page export — export any URL as HTML, PDF, or a full offline ZIP archive
  • Lighthouse performance audits — run accessibility, SEO, performance, PWA, and best-practices audits on any URL
  • Website crawling — crawl an entire site from a seed URL with configurable depth, path filters, and scrape options

Get started with the Browserless MCP Server →

Browserless Docs MCP​

A lightweight, read-only MCP server that gives your AI assistant direct access to the Browserless documentation. No API token required.

Use this when you need your AI to answer questions about Browserless — how to configure connections, which API endpoints to call, how to set up proxies, or any other documentation lookup.

Key capabilities:

  • Context-aware answers — ask questions about Browserless APIs, BrowserQL, configuration, and more
  • Zero configuration — no API token or authentication needed
  • Works everywhere — supports Cursor, VS Code, Claude Desktop, ChatGPT Desktop, Claude Code, and any MCP-compatible client

Get started with the Browserless Docs MCP →

Most users will want the Browserless MCP Server for its full browser automation capabilities. Add the Browserless Docs MCP alongside it if you also want your AI assistant to have instant access to Browserless documentation while coding.

Using Claude Code?​

If you specifically use Claude Code, there is also a dedicated Browserless Claude Code Plugin — a slash-command interface (/browserless:smart-scrape, /browserless:screenshot, etc.) backed by the Browserless REST APIs rather than MCP. Install it from inside Claude Code:

/plugin marketplace add browserless/claude-plugin
/plugin install browserless@browserless

Frequently Asked Questions​

What is MCP in the context of Browserless?

MCP (Model Context Protocol) lets AI agents interact with Browserless through a standardized interface. The Browserless MCP server exposes browser automation tools that AI models can call directly.

Which AI agents work with the Browserless MCP server?

The Browserless MCP server works with any MCP-compatible client, including Claude Desktop, Claude Code, Cursor, Windsurf, and other AI tools that support the Model Context Protocol standard.

Do I need a Browserless account to use the MCP server?

The Browserless MCP Server requires an API token for browser automation tasks. Sign up for a free account at browserless.io to get your token. The Docs MCP server, which provides documentation access only, does not require a Browserless token.