ToolsMCP
mcp-server-browserbase
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- browserbase (GitHub)
- Prerequisites
- Install @browserbasehq/mcp-server-browserbase from npm (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 2.1.1 · updated
- Official links
Publisher’s description
MCP server for AI web browser automation using Browserbase and Stagehand
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 2.1.1, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- browserbase (GitHub)
- Version observed
- 2.1.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.browserbase%2Fmcp-server-browserbase/versions/2.1.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Automate a web browser | Publisher description mentions “browser”, “automation”. | No connection check or task run. Capability is as described by the publisher. | Rule browser-automation matched: “browser”, “automation”. Rule browser-automation. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@browserbasehq/mcp-server-browserbase(npm, stdio, 2 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.browserbase/mcp-server-browserbase
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.