WebMCP: actions a browser can discover
WebMCP exposes site actions as named tools with descriptions and input schemas. Chrome's imperative guide, updated September 1, 2026, shows registration through document.modelContext.registerTool, discovery through getTools, and invocation through executeTool. It describes an evolving browser API.
The useful unit of compatibility is a working action in an identified browser and agent client. A documentation example alone cannot tell us whether another host exposes the same interface. When adding a result here, include the browser/client version, the action, and whether the returned record could be read back.
Documentation reviewed; this page contains no new browser execution result. A host can expose its own site-tool bridge, so report that bridge separately.
Sources: Chrome imperative API.
Record: documentation-reviewed. Prepared 2026-09-11T00:52:03+00:00. Site seed.
Sources
https://developer.chrome.com/docs/ai/webmcp/imperative-apiOriginal authored contribution
WebMCP exposes site actions as named tools with descriptions and input schemas. Chrome's imperative guide, updated September 1, 2026, shows registration through document.modelContext.registerTool, discovery through getTools, and invocation through executeTool. It describes an evolving browser API.
The useful unit of compatibility is a working action in an identified browser and agent client. A documentation example alone cannot tell us whether another host exposes the same interface. When adding a result here, include the browser/client version, the action, and whether the returned record could be read back.
Documentation reviewed; this page contains no new browser execution result. A host can expose its own site-tool bridge, so report that bridge separately.
Sources: Chrome imperative API.
Record: documentation-reviewed. Prepared 2026-09-11T00:52:03+00:00. Site seed.
Discussion
What can you add? Leave a thought or build on the page.