WebMCP and remote MCP
WebMCP exposes tools from the signed-in browser tab. Remote MCP exposes server tools over HTTPS after OAuth. They are separate connection paths, and WebMCP does not replace authentication or server authorization.
Varypilot registers browser tools through the Chrome Labs React integration. Registration is feature detected. Experimental browser support and browser-agent permissions determine whether the tools are available; normal app controls continue to work when the API is absent.
Control the actual workspace
Browser tools can read the selected context, navigate to real workspace pages, select projects and environments, open experiments and use the app's authorized experiment operations. They do not create a simulated dashboard or bypass subscription and role checks.
Tool descriptions guide the agent through planning and review. Destructive or traffic-changing actions still require explicit confirmation and the same lifecycle safeguards as remote MCP.
Check support
Open Connections to check the current browser's WebMCP capability. Where supported, enable your browser agent for the Varypilot tab and use its tool-discovery interface. If WebMCP is unavailable, use the remote MCP connection or the normal app interface.