Chrome for Developers Says WebMCP Does Not Replace MCP
Chrome for Developers says MCP connects agents to services, while WebMCP connects agents to an open website with the user in the loop.
On October 27, 2026 KST, Chrome for Developers posted that WebMCP does not replace MCP.
Image source: Chrome for Developers (@ChromiumDev)
Chrome for Developers stated that WebMCP is not replacing MCP and described how the two connect agents to different targets.
Different Connection Targets: Services and Open Websites
Chrome for Developers made it explicitly clear that WebMCP does not replace standard MCP.
According to the post, MCP connects agents to services. WebMCP connects agents to a website while it is open and the user is in the loop.
- MCP Connection Scope: Connects agents to services.
- WebMCP Connection Scope: Connects agents to a website while it is open.
The post presents these as different roles that fit together rather than one replacing the other.
Open Website and User-in-the-Loop Requirement
Chrome for Developers describes WebMCP as operating while the website is open and the user remains in the loop.
The source ties WebMCP to an open website and continued user involvement.
- Open Website Requirement: The website remains open while WebMCP connects the agent to it.
- User Involvement: The user remains in the loop.
These conditions distinguish WebMCP from MCP's connection to services.
How MCP and WebMCP Fit Together
Chrome for Developers explicitly said WebMCP does not replace MCP.
MCP connects agents to services. WebMCP connects agents to an open website with the user in the loop. The source presents these roles as fitting together.
- MCP Role: Connect agents to services.
- WebMCP Role: Connect agents to an open website while the user remains in the loop.