I think i've got it: WebMCP is the new web intents

Just over a month ago I wrote that WebMCP is the new web intents … maybe, but now I really do think that WebMCP is the new web intents (in a good way, not the “the entire project crashed and burned” way). While the spec says that this is not the intended goal, I think we have a federated way for the web to declare its capabilities and for someone (ideally you) to keep an index of them, and then to have your tools recall and re-use those tools when they can match the user’s (or their) intent with the capability of the page. webmcp-relay is a small MCP server that discovers the tools that a page exposes via “WebMCP” and can call them. You install it in your agent (Codex, Claude Code, whatever), and under the hood it uses Chrome DevTools MCP to actually run the browser. Install like this: { "mcpServers": { "webmcp-relay": { "command": "npx", "args": ["-y", "webmcp-relay", "--headless", "--channel", "canary"] } } } And when the agent opens a page via the relay, the relay asks DevTools to…