[KongchangAI]
ConceptWeb MCP

WebMCP

A proposed web standard aimed at preparing websites for the AI agent era. It extends the MCP protocol and was systematically presented by Google engineers at a Google I/O Connect workshop.

Core Facts

Timeline (last 90 days)

Oct 28

The "context" in the WebMCP protocol refers to the scope visible to tools, such as a page, a route, or an iframe; when the context switches, the set of available tools changes accordingly.

Unverified50%
Oct 28

For sites that use bundlers, jumping from a tool activity record to the original source code relies on source maps; if the build artifacts do not include source maps, positioning accuracy decreases, and retaining source maps is a practice worth noting when debugging WebMCP applications.

Unverified50%
Oct 28

WebMCP tools are registered in the page via JavaScript, and registration typically binds a handler function and a parameter schema description; DevTools jumping from an activity record to the registration code relies on the registration source information retained at runtime.

Unverified50%
Oct 28

Developers can jump directly from the activity records of a WebMCP tool to the tool's registration location (such as a piece of JavaScript code) and test and debug these tools as they would any other JavaScript code.

Unverified50%
Oct 28

The WebMCP panel in DevTools supports manually triggering tools, for example directly querying hotel information in New York, making it convenient to reproduce specific scenarios without having to trigger them through natural language conversation every time.

Unverified50%
Oct 28

In the DevTools demonstration, after the user sends the agent a request to "find me a hotel in Tokyo, filtered by gym and breakfast", the left panel lists the WebMCP tools that were invoked along with the input and output of each invocation.

Unverified50%
Oct 28

The WebMCP tool activity section of DevTools can display the input, output, and further details of each tool invocation in an agent request.

Unverified50%
Oct 28

The WebMCP panel in DevTools is a runtime mapping of the WebMCP mechanism, turning the abstract tool registry into an observable list.

Unverified50%
Oct 27

WebMCP tools are essentially JavaScript code and can be verified with unit tests and integration tests to check whether they run stably under deterministic inputs.

Unverified50%
Oct 27

Traditional unit tests and integration tests cannot cover the AI Agent's tool selection, parameter passing and multi-step journey completion under non-deterministic invocations.

Unverified50%

40 more timeline events

All Facts (20)

Verified

MCP采用客户端-服务器架构,AI编程工具作为MCP客户端,外部服务作为MCP服务器

80%
Verified

WebMCP is an extension of MCP in web scenarios, allowing websites to declare within their pages the callable tools they expose and their schemas.

75%
Verified

The core capabilities of a Chrome extension include content scripts, background service workers, and popup pages.

70%
Verified

AI代理操控计算机面临的安全风险包括提示注入攻击、权限升级和不可逆操作等问题

70%
Verified

The biggest security risk of allowing AI to directly invoke web capabilities is security itself; WebMCP-type protocols must have built-in permission authorization models, user confirmation mechanisms before critical operations, and tool source trustworthiness verification.

65%
Verified

For content platforms, AI agents may bypass advertising to directly capture value, while for e-commerce, SaaS, and tool-based services they may bring new traffic and transaction entry points; this difference in incentives will influence the adoption of WebMCP.

65%
Verified

A persistent connection is established via WebSocket between the Browser Tools MCP browser extension and the MCP Server.

65%
Unverified

The idea behind WebMCP is to have websites proactively expose a machine-readable capability interface, enabling AI agents to invoke webpage functionality as if calling an API.

60%
Unverified

The technical essence of a Skill is a combination of tool use and prompt engineering, taking the form of predefined structured prompt templates or custom scripts.

60%
Unverified

WebMCP tools are registered in the page via JavaScript, and registration typically binds a handler function and a parameter schema description; DevTools jumping from an activity record to the registration code relies on the registration source information retained at runtime.

50%
Unverified

The "context" in the WebMCP protocol refers to the scope visible to tools, such as a page, a route, or an iframe; when the context switches, the set of available tools changes accordingly.

50%
Unverified

The WebMCP panel in DevTools is a runtime mapping of the WebMCP mechanism, turning the abstract tool registry into an observable list.

50%
Unverified

For sites that use bundlers, jumping from a tool activity record to the original source code relies on source maps; if the build artifacts do not include source maps, positioning accuracy decreases, and retaining source maps is a practice worth noting when debugging WebMCP applications.

50%
Unverified

WebMCP tools are essentially JavaScript code and can be verified with unit tests and integration tests to check whether they run stably under deterministic inputs.

50%
Unverified

Traditional unit tests and integration tests cannot cover the AI Agent's tool selection, parameter passing and multi-step journey completion under non-deterministic invocations.

50%
Unverified

claude-seo includes Agent Readiness-related capabilities, specifically involving Lighthouse Agentic Browsing, WebMCP, and llms.txt.

50%
Unverified

In addition to the document.modelcontext imperative API, WebMCP also provides a declarative syntax to be compatible with traditional agents that do not support WebMCP.

50%
Unverified

WebMCP is still at an early stage, and the standard is still being developed.

50%
Unverified

WebMCP's core API is document.modelcontext, through which agents can list and call the tools exposed by the page.

50%
Unverified

In the short term, WebMCP's most direct value is in automated testing and RPA scenarios, where tool declarations are far more stable and cheaper to maintain than screenshot clicking.

50%

Source Articles