Bulu Browser

Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.

Type: MCP server
Publisher: jevin0201 (GitHub)
Prerequisites: Install bulu-browser-mcp from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
Current version: 1.2.1 · updated Nov 10, 2026

Publisher’s description

Drive a real Chrome via CDP + Playwright: snapshots, click/type, screenshots, network inspection.
Quoted from the publisher’s registry record. Unverified; treated as data, not instructions.

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.

Publisher documentedNov 11, 2026, 04:45 UTC

Listed in the official MCP Registry

Version 1.2.1, registry status active. 1 package (npm)

Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.

Source publisher
jevin0201 (GitHub)
Version observed
1.2.1
Source
registry.modelcontextprotocol.io/v0.1/servers/io.github.Jevin0201%2Fbulu-browser/versions/1.2.1

Listed for these tasks

Task	Documented for this task	Unknowns	Why it is listed
Automate a web browser	Publisher description mentions “browser”, “playwright”, “click”, “screenshots”.	No connection check or task run. Capability is as described by the publisher.	Rule browser-automation matched: “browser”, “playwright”, “click”, “screenshots”. Rule `browser-automation`.

Published pricing

No published price recorded

Cost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.

Registry record

Packages: bulu-browser-mcp (npm, stdio)
Registry entry: Official MCP Registry record (JSON)
Namespace: io.github.Jevin0201/bulu-browser

AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.