Site tools are ZeroTwo's support for the proposed WebMCP standard, which lets a page register actions that an agent can call while it shares your live, signed-in view. They work in the desktop app's built-in browser; the web app does not discover them.
WebMCP vs. MCP
MCP connects ZeroTwo to a local or remote server whose tools work without any open page. WebMCP instead has the site itself offer tools, which the browser finds when the page loads, so nothing is installed. It suits work in a shared view such as a canvas or dashboard, whereas an MCP server added as a connector or in a plugin suits integrations that must work with no page open. A site can offer both.
How it works in the browser
Open a site in the built-in browser. When the page has registered tools, a pointer icon labeled Site tools appears beside the address. Its popover lists Available site tools with a read and write count, and each tool expands to show its description and input schema. Tools disappear when you navigate away, and the list refreshes within a couple of seconds when a page changes its registrations.
Security and user controls
Treat tool names, descriptions, and results as untrusted. A tool's read-only label is set by the site and never grants permission to act. Check requests and results before you share sensitive data with a page.
To turn the feature off, switch off Enable site tools under Settings > Browser, in the Browser permissions group. Discovery and calls stop at once.
Limitations
Tools are read from the top-level page of the active browser tab only, and only desktop builds have this support. ZeroTwo's browser exposes Chromium's native WebMCP implementation, so what a page can register follows that API; the specification and Chrome's developer guide cover the details.
Add WebMCP to your website
Start from operations your site already supports, such as setting a dashboard date range, suggesting document edits, or comparing options in an itinerary, and expose them as tools. Describe each argument in its input schema, keep inputs narrow, state side effects in the description, and return results the agent can verify. Reuse your existing authentication and validation, and keep the normal interface for people and other clients. If you host the site on ZeroTwo, see Sites; the specification describes the registration API.