relevance to WebMCP

[elf-pavlik]

I've seen some recent work on https://webmachinelearning.github.io/webmcp/

As I understand at this moment agent using WebMCP would be either bundled together with a web browser or provided as a browser extension. I'm wondering if the web browser itself could act as an ACP client and then maybe something like MCP-over-ACP: MCP Transport via ACP Channels could expose WebMCP to the agent.

[jo32]

A browser-owned execution bridge is one workable arrangement. In DeepDeck, which I maintain, an Electron browser discovers the page's WebMCP tools while the agent runs in DeepSeek Harness. The browser handles page execution; the agent receives tool descriptions and results. Calls are bound to a tab, frame, document, and generated-tool revision so a navigation or replacement invalidates the affected operation.

The implementation overview and screenshots are here. We use a local Host/browser bridge, not ACP, so this does not establish MCP-over-ACP compatibility. For the proposed ACP design, the page identity and tool lifetime would need to remain explicit across that transport.