Guide / two ways to connect
WebMCP vs. hosted MCP
A website can expose tools in a supported browser, through a remote server, or both. Which you choose depends on whether the agent needs the page itself.
Hosted MCP: use an endpoint
A compatible MCP client connects to a server URL. The server can offer tools for tasks such as searching a catalog or looking up published services. The client doesn’t have to open the website page to call those tools.
Browser WebMCP: use the page
A site can make tools available in a compatible browser. The tool can act in page context, such as selecting an existing map result or preparing a supported form for review. This does not by itself create a remote MCP endpoint.
Start with one useful task
Choose a small, public task you can verify. The planned MCP for Sites flow starts with a free preview of suggested tools, before any subscription or script install. Site previews and checkout are not open yet.
For hosted tools, test connection, discovery and a known input. For browser tools, separately test execution in a compatible browser on the right page.