{
  "title": "WebMCP",
  "description": "Draft web-platform work for exposing website capabilities as tools to user agents and agent systems.",
  "slug": "webmcp",
  "locale": "en",
  "seoTitle": "WebMCP compatibility reference — Can My Agent Use",
  "socialTitle": "WebMCP compatibility",
  "socialDescription": "Draft maturity, web roles, and test boundaries for WebMCP.",
  "llmSummary": "WebMCP is draft W3C community-group work for websites exposing tools through web APIs and markup. Draft revision and browser/runtime flags are mandatory qualifiers.",
  "audience": "Web platform architects and agent-tooling engineers.",
  "contentKind": "specification",
  "status": "published",
  "tags": [
    "webmcp",
    "web",
    "tools",
    "draft"
  ],
  "updated": "2026-08-28T00:00:00.000Z",
  "published": "2026-08-28T00:00:00.000Z",
  "authority": "W3C Web Machine Learning Community Group",
  "revision": "2026-08-26 draft",
  "maturity": "draft community group report",
  "structure": "Web API and HTML/JavaScript tool exposure with web-platform tests",
  "sourceId": "S-074",
  "canonicalUrl": "https://webmachinelearning.github.io/webmcp/",
  "summary": "Let websites expose structured tools to compatible user agents.",
  "roles": [
    "website",
    "user-agent",
    "agent"
  ],
  "aliases": [
    "Web Model Context Protocol",
    "site tools"
  ],
  "body": "WebMCP sits at the website-to-agent boundary. It is not the same thing as configuring a remote MCP server, even when product language uses similar “tools” terminology.\n\nThe research snapshot records a draft Community Group Report. Any positive implementation assertion should name the draft revision, runtime or browser version, flags, origin/security conditions, and evidence class.",
  "html": "/specs/webmcp",
  "markdown": "/specs/webmcp.md",
  "json": "/api/v1/specs/webmcp.json"
}