ToolsMCP
chromium-bridge
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- dashi96 (GitHub)
- Prerequisites
- Install chromium-bridge from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.5.3 · updated
- Official links
Publisher’s description
MCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code: browser automation
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 0.5.3, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- dashi96 (GitHub)
- Version observed
- 0.5.3
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.dashi96%2Fchromium-bridge/versions/0.5.3
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Automate a web browser | Publisher description mentions “chromium”, “browsers”, “browser”, “automation”. | No connection check or task run. Capability is as described by the publisher. | Rule browser-automation matched: “chromium”, “browsers”, “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
chromium-bridge(npm, stdio)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.dashi96/chromium-bridge
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.