Your browser session
Keep the cookies, MFA, device trust, tabs, and authenticated state already present in the browser you normally use.
Open WebMCP bridge
Let agents use the browser you already trust.
webmcp-bridge connects WebMCP-capable pages in your existing browser to local AI agents, preserving your authenticated context without turning the bridge into a CDP automation layer.
Product boundary
Useful because it stays small.
The project does not scrape every tab, expose cookies, proxy network traffic, or hand agents a general browser debugger. WebMCP is the capability boundary.
WebMCP only
Agents receive only capabilities websites explicitly expose through WebMCP, not generic browser control.
Agent-first local interface
A compact Rust CLI emits JSON by default, while an MCP adapter serves clients that do not expose a shell.
No permanent daemon
The browser launches a tiny native host through Native Messaging only when the extension is connected.