From fc273f01fce602aaefc6f77ad10b68fccf3ff124 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20Beaufort?= Date: Wed, 18 Nov 2026 11:49:56 +0100 Subject: [PATCH] Link to the @w3c/webmcp-polyfill npm package Mention the polyfill in the README next to webmcp-types, and in the implementation status intro, noting that connecting to a browser agent still requires native browser support. --- README.md | 2 +- implementation-status.md | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index bf2dfb3..38ac820 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ WebMCP lets developers expose web application functionality as "tools"—JavaScript functions with natural language descriptions and structured schemas, designed for AI agent ingestion. These tools can be invoked by AI agents, including those built into the browser, hosted in iframes, or running in extensions to actuate web content that was traditionally designed for human interaction. A [declarative API](#future-exploration-declarative-api) based on HTML `
` elements is also being explored. -TypeScript type definitions for WebMCP are available in the [`webmcp-types`](https://www.npmjs.com/package/webmcp-types) npm package. +TypeScript type definitions for WebMCP are available in the [`webmcp-types`](https://www.npmjs.com/package/webmcp-types) npm package, and a polyfill is available in the [`@w3c/webmcp-polyfill`](https://www.npmjs.com/package/@w3c/webmcp-polyfill) npm package. See [Implementation Status](implementation-status.md) for browser and agent support, and [Best Practices](#best-practices) for guidance on designing effective tools. diff --git a/implementation-status.md b/implementation-status.md index fea6aec..ab5e616 100644 --- a/implementation-status.md +++ b/implementation-status.md @@ -2,6 +2,8 @@ This document shows the implementation status of WebMCP across different browsers and agents. +The [`@w3c/webmcp-polyfill`](https://www.npmjs.com/package/@w3c/webmcp-polyfill) npm package provides `document.modelContext` where it isn't natively available, so pages can register and test tools. Connecting to a browser agent still requires native browser support. + Brave logo OpenAI logo Chrome logo Edge logo Firefox logo Meta logo Safari logo # Brave