Enabling WebMCP Tools on my SvelteKit Migration Reference

An AI agent asks: "What's the Svelte 5 equivalent of useEffect?" Today it has two options — scrape the page HTML and parse it, or fetch api/data.json and filter 100+ items in context. Both work ok, but they both waste tokens. WebMCP gives our AI agent a third option: call get_svelte_equivalent({ framework: 'react', concept: 'Side Effects' }) and get a structured answer directly. The data is the same. The interface is purpose-built for agents. What WebMCP Is WebMCP is a W3C Community Group Draft that adds navigator.modelContext to browsers. It lets websites register MCP tools — the same protocol that powers Claude's tool use, Cursor's context, and other agent frameworks — directly in a webpage. An AI agent browsing the site can discover and call those tools without scraping. Chrome Canary (146+) has WebMCP behind a flag, and Microsoft Edge appears to support it out of the box — no flags or settings needed. For other browsers, @mcp-b/global from the MCP-B project fills in, until native s