W3C Standard · Chrome 146+

The open directory of
WebMCP-enabled websites

Discover websites that AI agents can interact with natively using the WebMCP protocol. No scraping, no hacks — structured tools in the browser.

0 sites
·
0 tools
·
0 categories

Browse by category

All Sites

Frequently Asked Questions
What is WebMCP? +
WebMCP is a W3C web standard that lets websites expose structured tools to AI agents running in the browser. Instead of scraping pages or clicking buttons, agents use the navigator.modelContext API to discover and call tools directly with typed parameters and get JSON responses back.
How does WebMCP work? +
Websites register tools using navigator.modelContext.registerTool() with a name, description, input schema, and handler function. When an AI agent visits the page, it reads available tools, picks the right one based on the description, calls it with structured parameters, and receives JSON output. Everything runs in the browser using the user's existing session.
Is WebMCP safe to use? +
WebMCP operates within the browser's existing security sandbox. Tools run in the page's JavaScript context with the same permissions as any other script — they cannot access other origins, other tabs, or escalate privileges. The browser shows users a consent prompt before any tool executes, and inputs are validated against JSON Schema before reaching the handler.
Which browsers support WebMCP? +
As of March 2026, Chrome 146+ Canary supports WebMCP natively behind the 'WebMCP for testing' flag. Edge support is expected soon since it shares the Chromium engine. A polyfill (MCP-B) is available for cross-browser support. The spec is being developed through the W3C Web Machine Learning Working Group.
How do I add WebMCP to my website? +
Add about 50 lines of JavaScript that calls navigator.modelContext.registerTool() with your tool definitions. Each tool needs a name, description, JSON Schema for inputs, and an async handler function. Your backend stays unchanged — WebMCP tools call your existing APIs from the frontend. See our step-by-step guide for full details.
What is the difference between WebMCP and MCP? +
WebMCP runs in the browser (client-side) and uses the user's existing session for authentication. Traditional MCP (Model Context Protocol by Anthropic) runs server-side with API keys or OAuth. They're complementary — many sites support both. WebMCP is best for user-facing websites, while MCP is best for developer tools and backend integrations.
Learn more
How to Add WebMCP to Your Website Best WebMCP Tools and Sites WebMCP Security The Future of WebMCP

Submit a site

Know a website that supports WebMCP? Add it to the directory. Submissions are reviewed before publishing.

What is WebMCP?

WebMCP is a W3C web standard that lets websites expose structured tools to AI agents running in the browser.

Instead of AI agents scraping pages and clicking buttons, WebMCP provides a clean API — navigator.modelContext — where websites register tools with typed inputs and outputs. AI agents discover these tools and call them directly.

🌐

For websites

Add ~50 lines of JavaScript to register your tools. Your backend stays unchanged — WebMCP tools just call your existing APIs from the frontend.

🤖

For AI agents

Discover and call tools on any page. Structured inputs, structured outputs. No DOM parsing, no brittle scrapers.

🔗

vs. MCP

WebMCP runs in the browser (client-side). Traditional MCP runs server-side. They're complementary — many sites support both.

Currently available in Chrome 146+ Canary behind a flag. Backed by Google and Microsoft, on track for W3C standardization.

Built by Andy · Build a microsite · Free VIN Decoder · QR Code Generator