How to connect the Browserless MCP server

Before you start

• A Browserless account, used for OAuth sign-in or to copy an API token from the account dashboard. docs.browserless.io/mcp
• Each tool call consumes Browserless units based on session time, plus proxy traffic and CAPTCHA solving if used. docs.browserless.io/mcp
• The hosted server uses the US West (San Francisco) Browserless region by default. London and Amsterdam endpoints are selected with the x-browserless-api-url header. docs.browserless.io/mcp
• On Claude Team and Enterprise plans an Owner adds the connector for the organization. ChatGPT custom MCP servers are limited to Business and Enterprise or Edu workspaces, and on Business only admins and owners can add them. docs.browserless.io/mcpdocs.browserless.io/mcp

Authentication

Your client → Browserless MCP

OAuth sign-in, handled by your MCP client. docs.browserless.io/mcpmodelcontextprotocol.io/specification

Browserless MCP → Browserless API

The server uses the API credential you supply. docs.browserless.io/mcp

Steps

1. Open Browserless's MCP setup instructions for your client

   docs.browserless.io/mcp/browserless-mcp-server/setup
2. Add the Browserless MCP server to your client

   Add https://mcp.browserless.io/mcp as a remote MCP server that uses the Streamable HTTP transport. The hosted server does not support the legacy SSE transport. Cursor users can install the Browserless plugin from the Cursor Marketplace instead.

   docs.browserless.io/mcpdocs.browserless.io/mcpregistry.modelcontextprotocol.io/v0.1
3. Sign in with your Browserless account
   docs.browserless.io/mcp
4. If your client can't use OAuth, use your API token

   Copy your API token from the Browserless account dashboard and send it in the Authorization header as a bearer token. For clients that only accept a URL, Browserless also accepts the token in a token query parameter; avoid this where a header is possible, because URLs are easily shared or logged.

   docs.browserless.io/mcpdocs.browserless.io/mcp
5. Only for the token alternative: Authorization
   registry.modelcontextprotocol.io/v0.1docs.browserless.io/mcp
6. Optional: regional Browserless endpoint
   registry.modelcontextprotocol.io/v0.1docs.browserless.io/mcp
7. List the server's tools

   Your client should list the server's tools. That confirms the connection, not every API permission.

   docs.browserless.io/mcp

What we observed

• 5 Nov 2026: HTTP 401 with WWW-Authenticate resource_metadata https://mcp.browserless.io/.well-known/oauth-protected-resource/mcp, which names the authorization server https://mcp.browserless.io and scope email.