Browserbase Remote MCP Server
Browserbase's hosted MCP gives agents cloud headless-browser sessions powered by Stagehand — navigate pages, extract structured data, take screenshots and automate web workflows at scale. Endpoint verified live on RemoteMCP.net (preflighted 200 OK).
- Provider
- Browserbase ↗
- Categories
- 🛠️ Developer Tools & Git🔌 Multi-App Gateways & Automation
中文简介
Browserbase 官方托管的远程 MCP 服务器。Browserbase 托管 MCP,为代理提供基于 Stagehand 的云端无头浏览器会话:网页导航、结构化数据提取、截图与自动化。
Maintainer of Browserbase? Claim or update this listing →
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"browserbase": {
"url": "https://mcp.browserbase.com/mcp"
}
}
}claude mcp add --transport http browserbase https://mcp.browserbase.com/mcp
Or add to .vscode/mcp.json:
{
"servers": {
"browserbase": {
"type": "http",
"url": "https://mcp.browserbase.com/mcp"
}
}
}- Open Settings → Connectors (Integrations) → Add Custom Connector.
- Paste the endpoint URL:
https://mcp.browserbase.com/mcp - No authentication needed — tools are available immediately.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"browserbase": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.browserbase.com/mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"browserbase": {
"serverUrl": "https://mcp.browserbase.com/mcp"
}
}
}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": {
"browserbase": {
"url": "https://mcp.browserbase.com/mcp"
}
}
}Add to ~/.codex/config.toml — Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.browserbase] url = "https://mcp.browserbase.com/mcp"
Add to cline_mcp_settings.json (Cline → MCP Servers → Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"browserbase": {
"type": "streamableHttp",
"url": "https://mcp.browserbase.com/mcp"
}
}
}Add to ~/.gemini/settings.json under mcpServers — httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"browserbase": {
"httpUrl": "https://mcp.browserbase.com/mcp"
}
}
}🧰 Browserbase MCP Tools & Schema (6)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| start ~131 tok | 🟠 Write | Create or reuse a Browserbase session | sessionId: string |
| end ~131 tok | 🟠 Write | Close the current Browserbase session | sessionId: string |
| navigate ~141 tok | 🟠 Write | Navigate to a URL | url*: stringsessionId: string |
| act ~144 tok | 🟠 Write | Perform an action on the page | action*: stringsessionId: string |
| observe ~150 tok | 🟠 Write | Observe actionable elements on the page | instruction*: stringsessionId: string |
| extract ~137 tok | 🟠 Write | Extract data from the page | instruction: stringsessionId: string |
🛡️ 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)
- Public read-only-friendly endpoint — no credentials stored client-side
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
🔐 OAuth 2.1 & Security
- Auth type
- None (public)
- Dynamic Client Registration
- —
- PKCE S256
- —
- Protected resource metadata
- https://mcp.browserbase.com/.well-known/oauth-protected-resource (expected location)
🧩 Recommended Agent Skills
📖 Browserbase MCP Endpoint Overview & Security Guide
Browserbase — Remote MCP Server
Browserbase's hosted MCP gives agents cloud headless-browser sessions powered by Stagehand — navigate pages, extract structured data, take screenshots and automate web workflows at scale. The remote endpoint means there is nothing to install — point your MCP client at the URL and start calling tools right away. Browserbase operates and versions the server themselves, so tool coverage tracks their API surface as it ships.
Official Browserbase Endpoint & Transport Architecture
- Endpoint URL:
https://mcp.browserbase.com/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. Browserbase does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
Browserbase is public and unauthenticated — no OAuth, no API key, no headers. Any MCP client can connect and call its tools directly, which also makes it a great endpoint for smoke-testing your own MCP client or proxy.
All 0 cataloged tools are read-only — Browserbase cannot mutate your account data, which makes it safe to connect broadly.
Common Troubleshooting & Connection Tips
- "Session expired" / stale
Mcp-Session-Id— just re-sendinitialize; stateless clients can ignore session headers entirely. - High-volume or production usage requires a Browserbase API key configured via client headers.
🚀 How to Connect
- Copy the Browserbase endpoint URLThe remote endpoint is https://mcp.browserbase.com/mcp.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http browserbase https://mcp.browserbase.com/mcp. Cursor: add"browserbase": { "url": "https://mcp.browserbase.com/mcp" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Verify with the online inspectorPaste https://mcp.browserbase.com/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Browserbase's 0 tools respond.
❓ FAQ
What is the Browserbase remote MCP endpoint?
The primary endpoint is https://mcp.browserbase.com/mcp. It is an official first-party server operated by Browserbase, speaking the Streamable HTTP transport.
How do I authenticate with Browserbase?
You don't — Browserbase is public and unauthenticated. Connect and start calling tools; no OAuth flow or API key is needed.
I'm getting a 401 Unauthorized from Browserbase — what's wrong?
Browserbase is authless, so a 401 is unusual. Check that you're hitting https://mcp.browserbase.com/mcp exactly (including the path) and not an API endpoint that requires a different credential.
Which MCP clients work with Browserbase?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http browserbase https://mcp.browserbase.com/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, Kiro (`~/.kiro/settings/mcp.json`), and Claude Desktop via the `mcp-remote` bridge.
What tools does Browserbase 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.