<- all tokdocs

WebMCP vs MCP: Sessions, Logged-In Browsers and Page-Scoped Tools

By , founder of Mavric and Apso

View on TikTok ->

MCP (Model Context Protocol) lets an AI agent call a service directly through a server, with no browser involved. WebMCP lets a web page register tools that an agent can call inside the user's own logged-in browser, and those tools change with the page. A TikTok from @agentic.conversations explains this split correctly, but says an MCP agent calls a service "through the session." The current MCP specification says the protocol is stateless and that an open connection is not a session.

What is the difference between MCP and WebMCP?

The clip puts it in one exchange. With MCP, "my agent doesn't need me" and "it probably doesn't even need to open a browser." With WebMCP, "my logged in session is what the agent now has access to," and "the tools that are available in that website are contextual."

Both halves of the WebMCP description match the WebMCP explainer maintained by the W3C Web Machine Learning Community Group.

Does WebMCP use your logged-in browser session?

Yes. The explainer's stated motivation is avoiding the need to "replicate the user's state, active context, and authentication credentials on a separate server." The agent works inside the page the user already signed into.

Are WebMCP tools specific to each page?

Yes. In the clip, the example is a shopping cart: "You're on the cart page. Yes. Here are the tools that are available to call." The explainer's guidance is nearly the same sentence: "Rather than registering a large catalog of tools upfront, dynamically register tools relevant to the active page state or workflow."

The mechanics:

  • A page calls registerTool() with a name, description, inputSchema and an execute callback.
  • It removes a tool with an AbortSignal when the tool no longer applies.
  • A toolchange event tells listeners the set of tools has changed.

Does MCP use sessions?

Not in the current specification. The MCP spec at revision 2026-07-28 has a section titled "Statelessness":

"The Model Context Protocol (MCP) is a stateless protocol: all the information needed to process a request is contained in the request itself. A server processes each request independently; no state should be inferred from previous requests, even those on the same connection or stream."

It adds that "an open connection, such as a STDIO process, is not a conversation or session." Servers "MUST NOT rely on prior requests over the same connection to establish context," and state that spans requests "MUST be referenced by an explicit identifier the client passes on each request." The architecture overview repeats it: every request carries its protocol version and capabilities in its _meta field.

The speaker's word choice has a history. The 2025-06-18 revision of the transports page had a "Session Management" section that defined an MCP session as "logically related interactions between a client and a server, beginning with the initialization phase." It used an Mcp-Session-Id header on the Streamable HTTP transport. That model is one revision old.

In practice, an MCP agent calling a remote service does not reuse a browser session or inherit the user's login. It sends independent JSON-RPC requests and authenticates under MCP's authorization framework for HTTP transports, with credentials given to the client separately. That gap is what WebMCP is designed to close.

How does the MCP architecture work?

The clip shows a diagram of a host with three MCP clients wired to three MCP servers, with a bracket labelled "Transport layer." It is a redraw rather than the official diagram, which shows four clients and three named servers. The structure it shows is right. The official overview says "The MCP host accomplishes this by creating one MCP client for each MCP server," and splits MCP into a data layer, which "Defines the JSON-RPC based protocol for client-server communication," and a transport layer.

Nothing in the diagram depicts a session, which fits the current spec better than the narration does.

How do you use WebMCP in Chrome?

Chrome's WebMCP documentation, last updated October 7, 2026, says it is available "from Chrome 149" through an origin trial. For local testing, turn on chrome://flags/#enable-webmcp-testing.

There are two ways to register tools. The "Imperative API" uses JavaScript to "Define different types of tools with standard JavaScript, such as form input, navigation tools, state management, or other functions." The "Declarative API" lets you "Add annotations to a standard HTML forms to create a WebMCP tool." Tool registration is controlled by the tools Permissions Policy, which "defaults to self."

The API surface has moved. The explainer now documents document.modelContext, not navigator.modelContext, so check which one your examples use.

Is WebMCP a web standard?

No. It is a Draft Community Group Report from the W3C Web Machine Learning Community Group. That is neither a W3C Recommendation nor on the W3C Standards Track.

About the video

The description says "Today is the last day of AgntCon + MCPCon North America in San Jose." The Linux Foundation lists AGNTCon + MCPCon North America on October 22 and 23, 2026, in San Jose, run by the Agentic AI Foundation with The Linux Foundation. The post went up on the morning of October 23. The end card names Angie Jones as a conference speaker, and the schedule lists her opening keynote on October 22.

The footage itself shows an outdoor residential street with no conference signage. The same organiser ran an event in Tokyo on September 10 and 11, 2026, where Angie Jones, Vice President of Developer Experience at the Agentic AI Foundation, gave the welcome keynote. Nothing in the frames shows where this conversation was filmed.

Bottom line

WebMCP runs inside the user's logged-in browser and exposes only the tools the current page registers. MCP connects an agent to services directly, and under the 2026-07-28 spec each request stands alone with no session. If you build for WebMCP, use document.modelContext and Chrome 149 or later.

Sources

Published October 23, 2026. Based on a TikTok by @agentic.conversations. Full video notes (markdown)