Browserless Remote MCP Server
Browserless's hosted MCP gives agents headless-browser automation โ navigate, scrape, screenshot and run Puppeteer/Playwright sessions against cloud Chrome instances. Endpoint verified live on RemoteMCP.net (preflighted 401/403 auth required).
- Provider
- Browserless โ
- Categories
- ๐ ๏ธ Developer Tools & Git
ไธญๆ็ฎไป
Browserless ๅฎๆนๆ็ฎก็่ฟ็จ MCP ๆๅกๅจใBrowserless ๆ็ฎก MCP๏ผไธบไปฃ็ๆไพๆ ๅคดๆต่งๅจ่ชๅจๅ๏ผๅฏผ่ชใๆๅใๆชๅพไธไบ็ซฏ Puppeteer/Playwright ไผ่ฏใ
Maintainer of Browserless? Claim or update this listing โ
๐ Client-side only โ never leaves your browser.
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"browserless": {
"url": "https://mcp.browserless.io/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}claude mcp add --transport http browserless https://mcp.browserless.io/mcp
With credential header:
claude mcp add --transport http browserless https://mcp.browserless.io/mcp --header "Authorization: Bearer YOUR_API_KEY"
Or add to .vscode/mcp.json:
{
"servers": {
"browserless": {
"type": "http",
"url": "https://mcp.browserless.io/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}- Open Settings โ Connectors (Integrations) โ Add Custom Connector.
- Paste the endpoint URL:
https://mcp.browserless.io/mcp - Provide your API key / Bearer token when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"browserless": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.browserless.io/mcp",
"--header",
"Authorization: Bearer YOUR_API_KEY"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"browserless": {
"serverUrl": "https://mcp.browserless.io/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"browserless": {
"url": "https://mcp.browserless.io/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Add to ~/.codex/config.toml โ Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.browserless] url = "https://mcp.browserless.io/mcp" bearer_token_env_var = "BROWSERLESS_TOKEN"
Add to cline_mcp_settings.json (Cline โ MCP Servers โ Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"browserless": {
"type": "streamableHttp",
"url": "https://mcp.browserless.io/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Add to ~/.gemini/settings.json under mcpServers โ httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"browserless": {
"httpUrl": "https://mcp.browserless.io/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}๐งฐ Browserless MCP Tools & Schema (0)
| Tool | Safety | Description | Parameters |
|---|
๐ก๏ธ Security, Quality & Context Token Audit
Every tool definition (name + description + input schema) is injected into your LLMโs context on every request โ Estimate per-call LLM token cost โ
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- Static credential (Bearer token / API key) โ protect it in client config
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
๐ OAuth 2.1 & Security
- Auth type
- API Key
- Dynamic Client Registration
- โ
- PKCE S256
- โ
- Protected resource metadata
- https://mcp.browserless.io/.well-known/oauth-protected-resource (expected location)
๐งฉ Recommended Agent Skills
๐ Browserless MCP Endpoint Overview & Security Guide
Browserless โ Remote MCP Server
Browserless's hosted MCP gives agents headless-browser automation โ navigate, scrape, screenshot and run Puppeteer/Playwright sessions against cloud Chrome instances. The remote endpoint means there is nothing to install โ point your MCP client at the URL and supply your credential as a bearer token. Browserless operates and versions the server themselves, so tool coverage tracks their API surface as it ships.
Official Browserless Endpoint & Transport Architecture
- Endpoint URL:
https://mcp.browserless.io/mcp - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Browserless does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
Browserless uses API-key authentication rather than OAuth. Get a key from https://www.browserless.io, then configure your client to send it โ most clients accept an Authorization: Bearer YOUR_API_KEY header, and mcp-remote supports --header arguments.
All 0 cataloged tools are read-only โ Browserless cannot mutate your account data, which makes it safe to connect broadly.
Common Troubleshooting & Connection Tips
- 401/403 responses โ your credential is missing or rejected. Regenerate the key/token and make sure it is sent as an
Authorization: Bearerheader on every request, including theinitializecall. - "Session expired" / stale
Mcp-Session-Idโ just re-sendinitialize; stateless clients can ignore session headers entirely. - Pass your API token as a Bearer header or ?token= parameter; OAuth is also supported.
๐ How to Connect
- Copy the Browserless endpoint URLThe remote endpoint is https://mcp.browserless.io/mcp.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http browserless https://mcp.browserless.io/mcp. Cursor: add"browserless": { "url": "https://mcp.browserless.io/mcp" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Configure your credentialGenerate an API key at https://www.browserless.io and add an
Authorization: Bearer <token>header to the server's config (supported by Cursor, VS Code, Windsurf and mcp-remote --header). - Verify with the online inspectorPaste https://mcp.browserless.io/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Browserless's 0 tools respond.
โ FAQ
What is the Browserless remote MCP endpoint?
The primary endpoint is https://mcp.browserless.io/mcp. It is an official first-party server operated by Browserless, speaking the Streamable HTTP transport.
How do I authenticate with Browserless?
Browserless expects a credential sent as an Authorization: Bearer header. Generate the API key in your Browserless account and add it to your client's headers.
I'm getting a 401 Unauthorized from Browserless โ what's wrong?
Your Bearer credential is missing, malformed or expired. Confirm it is attached to every request โ including initialize โ and that no proxy is stripping the Authorization header.
Which MCP clients work with Browserless?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http browserless https://mcp.browserless.io/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, Kiro (`~/.kiro/settings/mcp.json`), and Claude Desktop via the `mcp-remote` bridge.
What tools does Browserless expose?
0 tools are cataloged in this directory โ including . Use our online inspector to fetch the live tool list straight from the endpoint.
๐ Connect Guides
๐ Embed Status Badge in README
Related Servers
GitHub's official remote MCP server hosted at api.githubcopilot.com. Gives AI agents first-party access to repositories, issues, pull requests and code search.
Linear's official remote MCP server. Agents can search, create and update issues and query your team's workflow over Streamable HTTP or SSE.
Claude Skills's hosted remote MCP server. ClaudeSkills.club's public MCP lets agents search and pull from a catalog of 90,000+ Agent Skills (SKILL.md) โ workflow specs, safety scores and one-line install instructions. It is public and unauthenticated โ connect and call tools immediately.
GitLab's hosted remote MCP server. GitLab's official MCP server gives agents first-party access to repositories, merge requests, issues, pipelines and code search across gitlab.com and self-managed instances. It is protected by OAuth 2.1; compliant clients complete a browser consent flow with PKCE.