What is WebMCP? The New Browser Standard for AI Agents Explained

If you have been building with MCP servers in your code editor, you already know how powerful it is to give AI models direct access to tools and data sources. WebMCP takes that same idea and brings it to the browser.

MCP, Briefly

The Model Context Protocol (MCP) is an open standard created by Anthropic that lets AI models connect to external tools and data sources. Instead of copying and pasting context into a chat window, MCP servers expose structured tools that AI models can call directly.

For example, a Supabase MCP server lets an AI model query your database, run migrations, and manage tables -- all without you writing SQL by hand. MCP has taken off in code editors like Claude Code, Cursor, VS Code, and Windsurf. But until now, MCP has been limited to local development environments.

Enter WebMCP

WebMCP is a proposed browser API that exposes MCP-compatible endpoints from web pages. A website declares that it supports WebMCP, and an AI agent browsing that site can discover and use structured tools instead of scraping HTML or clicking buttons blindly.

graph LR
    subgraph Today["Today: Browser Automation"]
        A1[AI Agent] -->|Scrape HTML| B1[Web Page]
        B1 -->|Raw HTML/DOM| A1
    end

    subgraph WebMCP["With WebMCP"]
        A2[AI Agent] -->|Discover manifest| B2[Web Page]
        B2 -->|Tool schemas| A2
        A2 -->|Call tool| B2
        B2 -->|Structured JSON| A2
    end

How It Works

A website that supports WebMCP adds a manifest file (similar to a web app manifest) describing available tools. When an AI agent visits the site, it can:

1. Discover the WebMCP manifest at a well-known URL
2. Read the available tools and their schemas
3. Call those tools through a standardized HTTP interface
4. Receive structured responses instead of raw HTML

This is fundamentally different from web scraping. Instead of parsing DOM elements, the AI agent gets a clean, typed API.

A Concrete Example

Imagine an AI assistant helping users manage GitHub issues. Today, it either needs a GitHub MCP server (which works in a code editor) or it must automate a browser and click through the UI.

With WebMCP, GitHub could expose an MCP-compatible interface directly from github.com. The AI agent could call createIssue, listPullRequests, or addComment through the WebMCP API -- no browser automation, no API keys, no separate MCP server. Authentication flows through the browser's existing session.

Why This Matters

For Users

WebMCP means AI agents can help you on any website that supports the standard:

• Fill out complex forms by understanding fields semantically
• Navigate multi-step workflows without getting lost
• Extract structured data from dashboards and reports
• Perform actions on web apps with your existing authentication

For Developers

If you build web applications, WebMCP gives you a way to make your product AI-agent-friendly without building a separate API. You define tools once, and any AI agent that supports WebMCP can use them. This is similar to how adding structured data (JSON-LD) made websites machine-readable for search engines. WebMCP makes websites machine-actionable for AI agents.

For practical implementation details, see our WebMCP guide for React and Next.js. For ecommerce-specific patterns, see WebMCP for ecommerce.

For the MCP Ecosystem

WebMCP extends MCP beyond developer tools. Today, MCP servers are primarily used by developers in code editors. WebMCP opens the door for MCP to work across any web application, reaching a much broader audience.

Current Status

WebMCP is still in the proposal stage. The specification is being developed through the W3C Web Machine Learning Working Group.

Key milestones to watch:

• Specification drafts: The initial WebMCP specification is being circulated for feedback
• Browser experiments: Early prototyping is happening in Chromium-based browsers
• Website adoption: Early adopters are experimenting with WebMCP manifests

It is early, but the trajectory is clear. Just as MCP standardized how AI models talk to tools in development environments, WebMCP aims to standardize how AI agents interact with the web.

How It Relates to Existing MCP Servers

WebMCP does not replace existing MCP servers -- it complements them:

If you are using MCP servers in Cursor or Claude Code today, you will continue to do so. WebMCP adds a new surface for AI-web interaction alongside your existing setup. For a detailed side-by-side analysis, see WebMCP vs MCP or From MCP to WebMCP: both sides of the AI development coin.

What to Do Now

1. Follow the spec: Keep an eye on the W3C working group for updates
2. Experiment with MCP: Build and use MCP servers in your editor to understand the protocol. The patterns translate directly to WebMCP. Check out our curated stacks to get running in seconds.
3. Think about your web apps: Consider which parts of your application would benefit from AI-agent access and how you would structure those as tools
4. Join the discussion: The MCP community on GitHub and Discord is actively discussing WebMCP's design

The best preparation for WebMCP is getting comfortable with MCP itself. If you have not set up MCP servers in your editor yet, that is the place to start.

WebMCP is the next chapter of the same story. For now, MCP servers in your code editor are the practical path -- they work today, they are well-supported, and they make a real difference in your workflow.