W3C Web Machine Learning Working Group Standard

WebMCP.

Intelligence. Built into the DOM.

WebMCP (Web Model Context Protocol) is an open web standard proposed under the W3C Web Machine Learning Working Group (authored by Microsoft and Google) that enables front-end web applications to expose callable tools, prompts, and resources directly to AI browser agents via document.modelContext.

Proposed by Microsoft, Google, and the W3C WebML Working Group. Expose your web application's native functionality via document.modelContext so AI agents can actuate your site with zero scraping.

document.modelContext.executeTool("filter-templates")
200 OK • 4ms

Browser AI Agent Invocation

// Agent discovers & calls in-page tool
const tools = await document.modelContext.getTools();
const tool = tools.find(t => t.name === "filter-templates");

await document.modelContext.executeTool(tool, {
  "description": "Spring flyer with date"
});

Webpage Native Handler

// Page executes directly in client UI
execute({ description }) {
  filterTemplatesInUI(description);
  return {
    content: [{
      type: "text",
      text: "Updated canvas with 3 matching templates"
    }]
  };
}

The W3C Architecture

Built for the Browser Platform.

WebMCP bridges the gap between server-side Model Context Protocol and the living DOM.

document.modelContext

Standardized web platform interface proposed under the W3C WebML Working Group. Register, manage, and unregister tools imperatively or declaratively.

W3C WebML WG Draft

UI Synchronization.

Unlike backend MCP servers that bypass the browser, WebMCP executes in the user's tab, keeping active application state and visual UI in perfect sync.

Zero Context Divergence
🔒

Origin Isolation.

Enforces browser security boundaries. Same-origin documents share tools automatically; cross-origin frames require explicit allow="tools" Permissions Policy.

Permissions Policy: allow="tools"

Agent Ecosystem

Native to the World's Leading Agents.

When your website implements document.modelContext, AI browser agents call your actions directly instead of simulating mouse clicks or scraping HTML.

Dassi AI

Native WebMCP Engine.

Dassi is built from the ground up with a native tool.webmcp discovery engine. It automatically detects declared tools and invokes them in under 5ms with zero scraping.

Built-in tool.webmcp Supported
Claude Desktop

Seamless MCP Bridging.

Connect web pages directly to Claude Desktop and local LLM clients using standard Model Context Protocol servers and client transports.

Anthropic MCP Compatible Supported
Chrome & Microsoft

W3C Platform Standard.

Authored under the W3C WebML Working Group by Google and Microsoft engineers, establishing an open cross-browser specification for browser-mediated AI actions.

W3C WebML WG Draft Active
Automated Adoption

Let Dassi adapt your website to WebMCP.

Don't know where to start? Ask Dassi to inspect your web application. Dassi analyzes your UI elements, forms, and client state, and automatically drafts typed document.modelContext.registerTool() definitions ready to copy into your codebase.

"Dassi, generate WebMCP tool definitions for my website"

Implementation Standard

How to Adopt WebMCP in 3 Steps.

Implement the official W3C specification in your front-end codebase today.

// W3C WebMCP Standard Tool Registration
const controller = new AbortController();

await document.modelContext.registerTool({
  name: "search-products",
  description: "Search in-stock products by query and price filters",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "Search keyword" },
      maxPrice: { type: "number", description: "Optional max price in USD" }
    },
    required: ["query"]
  },
  async execute({ query, maxPrice }) {
    // Reuses existing client-side logic & updates page UI
    const results = await app.catalog.search({ query, maxPrice });
    return {
      content: [{ type: "text", text: JSON.stringify(results) }]
    };
  }
}, { signal: controller.signal });

// To unregister dynamically on page/modal close:
// controller.abort();

Live Diagnostic Utility

WebMCP Inspector.

Verify if your webpage properly implements the W3C WebMCP specification (document.modelContext).

Target: https://getwebmcp.dev W3C WebMCP Ready

✓ Verified document.modelContext Standard

Target exports valid tool registration handlers compatible with AI browser agents.

Ecosystem

Display the WebMCP Badge.

Let agents and users know your web application supports W3C WebMCP.

WebMCP Supported
[![WebMCP Supported](https://getwebmcp.dev/badge.svg)](https://getwebmcp.dev)

Questions & Answers

Frequently Asked Questions

What is the W3C WebMCP proposal?

WebMCP is an official web platform standard proposal authored by Microsoft and Google within the W3C Web Machine Learning Working Group (webmachinelearning/webmcp). It defines document.modelContext to let web pages expose client-side tools directly to AI browser agents.

How does WebMCP differ from Anthropic's server MCP?

Server MCP connects AI models to backend databases and local filesystems. WebMCP adapts this concept natively for browser tabs, allowing front-end applications to expose actions without writing a separate server daemon or replicating user authentication.

How do I use WebMCP before all browsers ship document.modelContext natively?

Include the lightweight universal polyfill shown in our Quickstart. It initializes document.modelContext and dispatches standard discovery events so AI browser agents (like Dassi AI and Chrome AI) can immediately discover your tools today.