chrome-bridge
Spec Support Unverified Confidence: Good (0.85)chrome-bridge is an MCP server published by frsorrentino; its MCP spec-revision support has not been verified yet. Last verified 2026-08-07.
Does chrome-bridge support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision chrome-bridge supports (as of 2026-08-07).
Is chrome-bridge a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for chrome-bridge (as of 2026-08-07).
How do I connect to chrome-bridge?
chrome-bridge is available via the package npm:chrome-bridge-mcp, the official MCP Registry under io.github.frsorrentino/chrome-bridge, the source repository at https://github.com/frsorrentino/chrome-bridge. Authentication: unknown. Transports: stdio.
When were chrome-bridge's facts last verified?
2026-08-07. Each fact on this page links to the sources used to verify it.
Your real, logged-in Chrome as an MCP server: 63 token-efficient web-dev tools. ChromeOS included.
How widely adopted is chrome-bridge?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
How was this verified, and what are the sources?
Verified · method: registry-record
· confidence 0.85 (Good).