What does an AI agent do today when it wants to book an appointment on your site? It takes screenshots, guesses what the buttons do, crawls the page's DOM, and simulates mouse clicks. Move a button in a redesign and the flow breaks. WebMCP is a new web standard designed to end this guessing game: the agent doesn't guess how your site works — your site tells it.
What Is WebMCP?
WebMCP (Web Model Context Protocol) is a proposed web standard that lets websites expose their JavaScript functions and HTML forms as "tools" that AI agents can use, complete with natural-language descriptions and structured schemas. It takes its name from the Model Context Protocol (MCP), which Anthropic started and which has become the de facto standard for connecting AI assistants to external systems. The difference: MCP requires a backend server, while WebMCP turns the page itself into an MCP server running inside the browser.
Where Did It Come From, and Where Does It Stand?
- The first draft was published in August 2025 by engineers from Google and Microsoft, within the W3C Web Machine Learning Community Group.
- The Chrome team announced an early preview in February 2026.
- Today it can be tested as an origin trial in Chrome 149 and Edge 150; ChatGPT Desktop supports WebMCP, and Brave's Leo assistant has experimental support.
- Standards-position discussions are ongoing at Firefox and Safari.
In other words, WebMCP isn't yet a standard "everyone uses" — but the two most widespread browser engines and a major AI client are at the table. This is exactly the window where first-mover advantage is earned.
How Does It Work? Two Approaches
1. The Declarative API: Using Your Existing Forms
The easiest starting point is adding a few attributes to the HTML forms you already have:
<form toolname="request-appointment" tooldescription="Requests an initial consultation appointment at the clinic"> <input name="name" required toolparamdescription="The patient's full name"> <input name="date" type="date" required toolparamdescription="Preferred appointment date"> <button type="submit">Request Appointment</button> </form>
toolname tells the agent the tool's name, tooldescription what it does, and toolparamdescription what each field means. Without the toolautosubmit attribute, the agent fills in the form but the decision to submit stays with the user — the right default for sensitive actions.
2. The Imperative API: Using JavaScript
For more complex flows, you define the tool directly in JavaScript:
await document.modelContext.registerTool({ name: "search-products", description: "Searches the catalog and filters by query and maximum price", inputSchema: { type: "object", properties: { query: { type: "string", description: "The product to find, e.g. 'porcelain dinnerware set'" }, maxPrice: { type: "number", description: "Upper price limit in USD" } }, required: ["query"] }, async execute({ query, maxPrice }) { const results = await searchCatalog(query, maxPrice); updateUI(results); return { content: [{ type: "text", text: JSON.stringify(results) }] }; } });
The key point: the tool calls the search function your site already has and updates the screen too. The user keeps seeing what the agent is doing on the page, and you don't have to write a separate backend.
Note: WebMCP is still a draft; API names and details may change. Check the current specification and the origin trial terms before using it in production.
Security: Can an Agent Do Anything on My Site?
No — and that's by design:
- WebMCP is built not for fully autonomous agents but for human-in-the-loop flows where the user is present in the browser.
- It's gated by a Permissions Policy called
tools: by default only the site's own origin can expose tools, and third-party iframes can't register tools without explicit permission (allow="tools"). - You decide what each tool does. For irreversible steps like payments, deletions, or contract approvals, leaving the final confirmation to the user is in your hands.
Which Flows on Your Site Should Become "Tools"?
| Page / Flow | Suggested WebMCP tool | Priority |
|---|---|---|
| Contact / quote form | request-quote (service, budget, timeline) | High — the easiest win |
| Booking / reservation | request-appointment (date, party size) | High |
| Product search and filters | search-products (query, price, size) | High (e-commerce) |
| Add to cart | add-to-cart (product, variant, quantity) | Medium — with user confirmation |
| Order tracking | order-status (order number) | Medium |
| Payment | Route the user to the checkout step instead of exposing a tool | Should stay under user control |
The Three Layers of Agent Readiness
WebMCP isn't a magic wand on its own; it's the third layer of getting your site ready for the agent era:
- Being understood: Clean HTML, speed, structured data (schema.org), and an llms.txt and GEO foundation. Does the agent know what your site is?
- Being trusted: A consistent brand profile, accurate pricing and stock, clear policies. Is the agent comfortable recommending you?
- Being usable: WebMCP tools and, where needed, backend MCP or commerce protocols like UCP. Can the agent finish the job on your site?
Most businesses still have gaps in the first layer. Starting there also makes the move to WebMCP easier — because a well-labeled, accessible form is already halfway to being a WebMCP tool.
Frequently Asked Questions
Does adding WebMCP affect regular users? No. Browsers that don't support WebMCP ignore the attributes and registered tools; the site keeps working the same way for everyone (progressive enhancement).
What's the difference between WebMCP and MCP? MCP is an AI platform connecting to your backend server. WebMCP exposes tools inside the page, alongside the user's session and screen. They're complementary, not alternatives.
Should I add it now, or wait until the standard is final? The declarative attributes are low-cost and easy to roll back, so trying them on contact and booking forms today makes sense. For complex imperative tools, it's safer to follow the origin trial and move step by step.
Conclusion
The web was designed for people; in 2026, sites have a second audience: AI agents getting things done on their users' behalf. WebMCP is the first standard way to tell that audience "here's how to use my site." At Senyo Labs, we see agent readiness as the natural continuation of SEO and GEO work; if you'd like to assess which of your site's flows are ready to open up to agents, schedule a free consultation.