Key Takeaways
- WebMCP is an emerging browser standard that lets AI agents actually use a website’s features, not just read its text.
- It is a W3C Web Machine Learning Community Group proposal backed by Google and Microsoft, and it is still early, not a ratified standard.
- It works client-side: a page registers tools the agent can call, so the agent acts through your real interface instead of a separate backend server.
- WebMCP sits next to llms.txt and schema. Those help AI read and cite you; WebMCP is about letting AI take actions.
- On WordPress, the free RankReady plugin already publishes a WebMCP manifest at /.well-known/mcp.json, so you can signal agent-readiness today.
A few months ago I watched an AI assistant try to book a demo on a client’s WordPress site. It read the page perfectly. It summarised the pricing, quoted the feature list, even located the contact form. Then it stopped. It could describe the button, but it could not press it. The whole site was readable and none of it was usable.
That gap is exactly what WebMCP is trying to close. For the last two years the AI-readiness conversation has been about making your content easy to read and cite, with llms.txt, clean Markdown, and schema. WebMCP is the next layer: making your site easy to operate. This guide explains what WebMCP is in plain English, how it differs from the Model Context Protocol and llms.txt, and how a WordPress site can start signalling that it is ready for agents.
What Is WebMCP?
WebMCP is a proposed browser standard that lets a website expose its own functionality, either JavaScript functions or HTML form elements, as tools that an AI agent can call. Each tool gets a natural-language description and a structured input schema, so an agent in the browser can understand what the tool does and run it.
The mechanism is client-side. A page registers its tools through a browser interface (the current draft uses document.modelContext with a registerTool call), and an agent acting on behalf of the user can discover and invoke them. The agent works through your real interface, with your existing code and the user’s existing login session, instead of going around your site to a separate backend.
Two facts worth being precise about. WebMCP is a proposal under the W3C Web Machine Learning Community Group, with contributors from Google and Microsoft and an evolving specification draft. It is early. The simplest way to hold it in your head: llms.txt and schema make your content readable; WebMCP makes your site operable.
WebMCP vs MCP vs llms.txt: the read-to-act layers
It is easy to lump every AI acronym together. They actually do different jobs, and they stack rather than compete.
| Layer | What it does | Where it lives |
|---|---|---|
| llms.txt / Markdown | Hands AI a clean, machine-readable copy of your content for reading and citation | Files served from your domain |
| Schema (Article, FAQ, Speakable) | Adds structured meaning so search and AI answers understand your content | In-page JSON-LD |
| MCP (server) | Connects an AI model to a backend or external tool over a server | A separate MCP server |
| WebMCP (browser) | Exposes the page’s own actions to an agent running in the browser | Client-side, inside the page |
The cleanest distinction is between MCP and WebMCP. A traditional MCP server bypasses your web interface and often forces you to duplicate your backend logic, your data, and your authentication on a separate server. WebMCP reuses what you already have: the same client-side code, the same UI, and the same session the user is already logged into. One is server-to-server plumbing; the other lives where your visitor and their agent already are.
Also Read: What Is the Model Context Protocol (MCP)? for the server-side side of this story and where it fits on WordPress.
Why WebMCP Matters for WordPress Site Owners
Search behaviour is moving from “type a query, scan results, click” to “ask an agent to handle it.” When that happens, the question is no longer only whether an AI can find and quote your page. It is whether an AI can complete a task on your site on a visitor’s behalf.
If agents can only read you, you are a reference they cite and then leave. If agents can act on your site, you stay a destination where things actually get done. For a WordPress site that could mean filtering a product catalogue, starting a booking, running an internal search, or beginning a checkout, all through your real interface with the user watching it happen rather than being sent to some opaque backend.
This is the same strategic reason the AI-readiness conversation matters at all. Being readable got you cited. Being operable keeps you useful once the agent is the one driving.
How WebMCP Works on a WordPress Site
At a high level the flow has three parts. First, the page registers its tools, describing each action in plain language with a schema for its inputs. Second, an agent discovers what is available. Third, the agent calls a tool, your existing JavaScript handles it, and the interface updates the way it normally would.
Discovery is where a manifest comes in. A file published at /.well-known/mcp.json advertises that your site speaks this language and points to what it offers. You do not want to hand-write and maintain that file across a WordPress site by hand, which is exactly the kind of plumbing a plugin should handle for you.
Getting WebMCP-Ready on WordPress
You do not need to write the manifest by hand. RankReady, a free WordPress plugin, publishes a WebMCP manifest at /.well-known/mcp.json for Model Context Protocol integration, alongside the rest of your discovery files: llms.txt and llms-full.txt following the llmstxt.org standard, Markdown endpoints that serve each post as clean .md, and Open Knowledge Format output.
The point is to treat WebMCP as one signal in a fuller picture rather than a standalone trick. Reading first, then action. RankReady pairs the manifest with 31 individual AI crawler controls, Article and Speakable schema, a per-post AI readiness scorecard that grades 22 signals, and AI referral tracking from ChatGPT, Perplexity, Claude, Gemini, and Copilot. It is free forever, GPL-2.0, runs on WordPress 6.0+ and PHP 7.4+, keeps zero telemetry, and works alongside Rank Math, Yoast, AIOSEO, SEOPress, and others rather than replacing them.
Also Read: The 2026 AI-Readiness Stack for WordPress shows how llms.txt, schema, MCP, and OKF fit together with WebMCP.
The Honest Take: WebMCP Is Early
WebMCP is a proposal, not a finished web standard. The API names will change, browser support is experimental, and nobody should rebuild their site around it this quarter. Treat it as forward positioning, not a feature you ship and forget.
What is worth doing now is sequencing it sensibly. Get readable first with llms.txt and schema so agents can understand you. Publish the manifest so you are discoverable as agent-ready when the spec matures. Then watch the W3C group as it evolves. And keep one thing honest: no plugin makes a thin site worth acting on. WebMCP is a capability and signal layer, not a shortcut around having something useful to offer.
Suggested Reading
- What Is the Model Context Protocol (MCP)? A WordPress Guide
- MCP vs API: What’s the Difference, and When Your WordPress Site Needs Each
- The 2026 AI-Readiness Stack for WordPress
- llms.txt for Gutenberg WordPress
- Generative Engine Optimization (GEO): The 2026 WordPress Guide
