Browserless: MCP server, setup and security

What Browserless does

According to its repository: “Headless browser automation and web scraping via the Browserless smart scraper API.”

The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Browserless is listed under Browser automation, a category of 109 servers in the directory, where it ranks #94 by stars.

Installing and connecting Browserless

Distribution modes declared in the official MCP registry:

• npm package (Node.js, usually started with npx)
• remote server (streamable-http): you connect to it by URL, with nothing to install locally

It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: TypeScript.

The registry lists one secret variable to provide (API key, access token). Keep them in the client's environment variables, never in a shared file or a repository.

Security: what to check

Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.

Points found for Browserless:

• System access: the Browser automation category gives the agent control over files, a terminal, code or a browser. A booby-trapped instruction in content the agent reads (prompt injection) can then turn into an action.
• Secrets: the server acts with your credentials. Create a dedicated key with minimum rights and an expiry date.
• No licence: without a licence the code is not legally reusable, even if it is public. Avoid it in a company setting without the author's agreement.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on February 20, 2026, the browserless/browserless-mcp repository has 8 stars and 4 forks, with 0 open issues. It has more stars than 22% of the servers in the directory. It received changes this month. Version published in the registry: 1.39.0 (October 16, 2026).

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.