WebMCP
Is Not MCP!!

A proposed browser standard that exposes a site’s features to the browser’s built-in AI agent. The browser finally has a job description.

An open protocol connecting AI apps to external tools, data, and workflows. The server has a whole career outside your tab.

Not MCP. Browser-native and tied to the tab.

Not WebMCP. Connected to a server and independent of the tab.

Ephemeral: its tools exist while the page is open. Close the tab and WebMCP packs up its little office.

Persistent: a server or daemon can stay available without a website open. It has keys to the building.

Browser-specific: it can use live page, DOM, and session context. Close the tab, and the context goes with it.

Platform-independent: agents can connect from desktop, mobile, cloud, or web environments. It does not care which tab you left open.

WebMCP, not MCP. The website owns the UI. The agent is just visiting.

MCP, not WebMCP. The tools can work independently of your website. No tab required.

Browser-integrated and DOM-aware: the agent interacts with your existing website. The agent is the guest now, so please hide the laundry.

Headless and external: tools act on services behind the interface. It does not need to admire your beautifully rounded buttons.

Tools register on the webpage during the user’s visit, through JavaScript or HTML. No visit, no tools; the bouncer is strict.

Tools are discovered through a connection between an MCP client and server. There is paperwork, but at least the paperwork is standardized.

Best for live website tasks while the page is open: navigate, search, update, submit. No robot mouse required.

Best for background API actions, data retrieval, and workflows. It can keep working while your browser is taking a nap.

Browser APIs inspired by MCP, not a JavaScript remake of MCP. They leave out server-side concepts because the tab has enough going on.

A broader client-server protocol, not a browser API. It has no interest in pretending to be your website.

Works alongside MCP: WebMCP handles the contextual live UI while the user is there. Coworkers, not identical twins.

Works alongside WebMCP: MCP connects agents to external tools and services. Finally, a division of labor.