WebMCP vs Relay

Let AI control your browser securely

Use AI on real websites with per-tab access, live activity visibility, and one-click disconnect. When a site exposes native browser tools, use them. When it does not, Relay keeps the session connected and under control.

Controlled Access

Grant AI access to a single active tab, while other tabs, history, passwords, and bookmarks stay out of reach.

Visible Sessions

Watch actions live in the activity log and cut the connection with one click.

Coverage Beyond Native

Handle pop-ups, new tabs, restrictive networks, and long-running sessions, even on sites with no WebMCP support.

How ProxyBase Relay complements WebMCP

WebMCP natively exposes structured tools inside the live tab. Relay provides orchestration across tabs, deep observability, and extensive coverage for non-compliant sites.

Topic
WebMCP
ProxyBase Relay
Core modelNative browser standard for websites to expose structured tools to the browser agent in the active tabBrowser extension bridge that connects AI assistants to the browser with CDP-style control and session features
Depends on site adoptionYes, the website has to expose WebMCP toolsNo, it can still operate on sites that have not implemented WebMCP
ScopeFrontend, live-tab, page-scoped actionsLive browser session control across tabs, pop-ups, and ongoing sessions
User control featuresChrome docs focus on tool exposure and execution, not Relay-style monitoring or kill switch controlsPer-tab permissions, activity log overlay, one-click disconnect
Multi-tab and pop-upsNot the main value proposition in the Chrome guidanceExplicitly handles new tabs and social-login pop-ups with tab multiplexing
Long-running sessionsTab-bound and ephemeral while the page is openDesigned to keep a continuous connection tunnel alive for longer tasks
Best fitSites that intentionally expose clean, structured actionsReal-world browser work where sites are inconsistent, legacy, or not WebMCP-enabled
Start with one tab