WebMCP vs Anthropic MCP vs Microsoft NLWeb — Which Do You Need?
The three standards solve different problems in the AI-web stack. Pick the wrong one and you rebuild in six months. Here is the simple decision framework.
Three big standards showed up for the "let AI agents use the web" job in late 2025 and early 2026. They look similar in marketing copy and are wildly different in practice. Picking the right one up front saves you a rebuild later.
The short answer
- WebMCP (Google, 2026) — client-side, runs in the browser, uses the logged-in user's session and permissions. Best for: any site with a UI.
- Anthropic MCP (2024) — server-to-server, the model connects to your backend via stdio or HTTP. Best for: internal tools, APIs, data access.
- Microsoft NLWeb (2025) — natural-language queryable endpoints, REST-style, schema-driven. Best for: structured content sites (catalogs, knowledge bases).
Side-by-side comparison
| Attribute | WebMCP | Anthropic MCP | Microsoft NLWeb |
|---|---|---|---|
| Runs on | Browser (client) | Backend server | Backend server |
| Auth model | User session (cookies) | API key / service auth | Public or API key |
| Primary protocol | navigator.modelContext | JSON-RPC over stdio/HTTP | REST + JSON schema |
| Data source | Whatever the page can see | Whatever the server exposes | Structured content |
| Setup effort | Low (HTML attributes) | Medium (server code) | Medium (schemas) |
| Browser needed | Chrome 146 Canary (2026) | No | No |
| Human-in-the-loop | Built-in | Optional | Read-only |
When to use WebMCP
Use WebMCP when the thing you want to expose is already a UI. E-commerce cart, booking flow, contact form, dashboard action, multi-step wizard. The browser is doing the hard work already — WebMCP just tells the agent "this form does X." No new backend, no new auth, no new infrastructure. You can ship the Declarative API in an afternoon.
When to use Anthropic MCP
Use Anthropic MCP when the agent needs to access data or capabilities that have no UI. Examples: a company knowledge base, a developer's local filesystem, a database, a CI system, an internal HR tool. MCP is the right fit when the agent is calling your service directly — typically inside Claude Desktop, VS Code, or a custom agent harness — and no browser is involved.
When to use Microsoft NLWeb
Use NLWeb when you publish structured content at scale: a product catalog, a documentation site, a jobs board, a real-estate listings site. NLWeb lets agents query that content in natural language and get back strongly-typed results. It's effectively "a search API, but the query is a sentence."
The honest answer most teams arrive at
You'll probably deploy all three. They are not competitors — they are layers:
- NLWeb for "what do you have?" (discovery, read)
- WebMCP for "do it for the signed-in user" (action, write)
- Anthropic MCP for "do it programmatically without a browser" (automation, integration)
A well-instrumented e-commerce site in 2026 publishes NLWeb endpoints for its catalog, implements WebMCP on checkout and account forms, and exposes MCP servers for partners and internal agents. Each one serves a distinct class of agent.
Where to start
If you can only do one this quarter, start with WebMCP. It has the lowest implementation cost (two HTML attributes per form), the biggest user-facing win (your site becomes agent-accessible), and it's the layer that directly moves revenue because it touches conversion actions. Run the free readiness audit to see where you stand.
For implementation details, see the full WebMCP guide. For the API surface, read the navigator.modelContext reference. For strategy, start with AEO.
Frequently Asked Questions
Are WebMCP and Anthropic MCP compatible?
They share some conceptual DNA (both describe tools with name, description, input schema) but they are not wire-compatible. An Anthropic MCP client cannot connect to a WebMCP-enabled page directly; the browser is the integration layer.
Will WebMCP replace Anthropic MCP?
No. They solve different problems. WebMCP is for user-facing browser actions; Anthropic MCP is for backend tool calling. Most production AI systems will use both.
Does NLWeb need a Microsoft stack?
No. NLWeb is an open protocol — you can implement it on any backend. Microsoft open-sourced the reference implementation in late 2025.
Which one is easiest to ship first?
WebMCP by a wide margin. For any site that already has HTML forms, you add two attributes and you are done with the basics.
Do I need a server for WebMCP?
Only the server you already have. WebMCP runs entirely in the browser — your backend receives normal form submissions or fetch calls. No separate MCP server is required.
Is your site ready for AI agents?
Run a free WebMCP readiness audit in 15 seconds — no signup.
Run Free Audit →