WebMCP Doesn't Replace MCP—So What Is It For?

On October 26, the official Chrome for Developers account posted a tweet specifically to clear up a claim: WebMCP does not replace MCP.

The original wording was brief:

MCP connects AI agents to your services.
WebMCP connects AI agents to the website you currently have open, with the user present throughout.

The two are not the same thing, nor are they a replacement relationship. MCP is aimed at backend services, while WebMCP is aimed at the page the user is currently viewing in the browser.

In the comments, one developer summed up the division of labor in a sentence: MCP is the front door to the backend, and WebMCP is the tab the user is staring at. Others said MCP handles background tasks, while WebMCP handles what the user is currently looking at. A developer who builds free WebMCP tools said the two have completely different use cases, and that the official account continuing to clarify this is a good thing.

A few concrete scenarios make this distinction tangible.

Security is one. A developer said the most valuable part of WebMCP is that the agent only inherits the permissions already available in the user's current session, and the user can see in real time what it is doing. This makes it easier for security teams to accept.

Unsaved data is another. A developer pointed out that unsaved forms contain values that only the page has, and server-side APIs cannot access them. This is a concrete reason for WebMCP to exist.

There is also an edge case: can WebMCP still be used when the tab is not visible in the background? Someone mentioned that when browser agents upload files on Instagram and TikTok, they get stuck if the tab is hidden. How strict the "page stays open" requirement is remains unclear.

There was skepticism too. Some believe many websites already have mature APIs, so there is no need to build a separate layer for WebMCP. Others joked that this is just one more layer to debug for Chrome extensions.

Where the boundary lies was the hardest part of the discussion. A developer used a note-taking app as an example: "Add this sentence to the note I'm editing" is suitable for WebMCP; "Look up what decisions I made last month" is suitable for going through MCP's memory service, and it would be best to store the source and date along with it.

WebMCP is still early. The fact that Chrome's official account was willing to post a dedicated clarification shows that this direction has value, and that there is also considerable confusion. What is worth watching next is whether website developers will actually build an interface layer for "the page the user is currently viewing," or continue to let traditional APIs handle everything.