THE WEBMCP INDUSTRY LANDSCAPE

Know who is building what.

The standards, browser teams, open protocol foundations and industry resources shaping the move towards an agent-ready web.

Four different roles. One changing web.

Explore the landscape ↓
WebMCP across connected digital experiences

START WITH THE DISTINCTION

There isn't one company behind WebMCP.

WebMCP is an emerging web capability being developed through an open standards process and implemented experimentally by browser and developer teams. MCP is a separate, complementary protocol for connecting AI applications to external tools and systems.

To understand the industry, it helps to distinguish the people developing the web standard, the browser teams implementing it, the foundation stewarding MCP, and independent services that help people discover the ecosystem.

FOUR INDUSTRY REFERENCES

Who they are. What they do. What they offer.

These organisations and resources have different responsibilities. They are not interchangeable, and none should be mistaken for the sole owner of WebMCP.

01 · WEB STANDARDS

W3C — World Wide Web Consortium

W3C is an international public-interest non-profit where member organisations, staff and the wider community develop open web standards. Its work helps keep the web interoperable, accessible, secure and usable across platforms.

Its WebMCP connection

The Web Machine Learning Community Group is the community space where the WebMCP proposal is being developed. The proposal is not the same thing as a finished, universally implemented web standard.

What W3C offers

  • Open standards specifications and technical discussions.
  • Working groups and community groups.
  • Participation pathways for organisations and individuals.
  • Standards work covering accessibility, privacy, security and interoperability.

Industry role: open web standards and community development.

02 · BROWSER AND DEVELOPER PLATFORM

Google Chrome for Developers

Google's Chrome developer organisation publishes browser documentation, APIs, developer tools, experiments and implementation guidance. It helps web developers understand what Chrome supports and how to build for it.

Its WebMCP connection

Chrome engineers are contributing to WebMCP development and publishing implementation guidance, examples and experimental access information. Browser support and feature availability can change, so developers must check the current documentation and test the actual target environment.

What Google offers

  • WebMCP documentation and technical explainers.
  • Chrome developer tools, samples and reference implementations.
  • Early Preview and Origin Trial information where available.
  • Browser platform documentation, testing and developer community resources.

Industry role: browser implementation, developer enablement and experimentation.

03 · OPEN PROTOCOL STEWARDSHIP

Agentic AI Foundation and Model Context Protocol

MCP is an open protocol that standardises how AI applications connect to external tools, data sources and services. It is complementary to WebMCP: MCP connects beyond the page, while WebMCP exposes capabilities from the website in the browser context.

Who stewards it

The Model Context Protocol was donated to the Agentic AI Foundation (AAIF), a directed fund under the Linux Foundation. The foundation provides a neutral home for open agentic AI projects. Anthropic, Block and OpenAI were founding contributors, with support from major technology organisations.

What the ecosystem offers

  • Open protocol specifications and SDKs.
  • Server and client implementation patterns.
  • Developer documentation, examples and community contribution.
  • A growing ecosystem of tools, integrations and events.
  • Foundation-level collaboration and project stewardship.

Industry role: open protocol ecosystem and neutral project stewardship.

04 · INDEPENDENT INDUSTRY DIRECTORY

WebMCP.com — maintained by nekuda

WebMCP.com is an independent directory and discovery service. It is not the standards body and does not define the WebMCP specification. It describes itself as a live directory of websites exposing WebMCP tools to AI agents.

What the service offers

  • Discovery of websites and platforms exposing WebMCP tools.
  • Inspection of agent-readable tools and input schemas.
  • Directory views across industries and technology platforms.
  • Resources for developers building and improving WebMCP tools.
  • Links to tools, talks, frameworks and community resources.

How to use it

Use it to research adoption, inspect public examples and discover patterns. Treat directory counts and classifications as the service's own indexed data, not as independently audited industry-wide adoption figures.

Industry role: independent discovery, ecosystem visibility and developer resources.

Important: W3C and the Web Machine Learning Community Group are the standards-development reference for WebMCP. Chrome is a major implementation and developer resource. MCP is a related but distinct protocol under AAIF stewardship. WebMCP.com is an independent directory. Check each source for its current status, claims and terms before relying on it.

HOW THE PIECES FIT TOGETHER

Different layers. Complementary jobs.

W3C / WebMCP

Defines and develops the browser-facing web capability through an open standards community.

Chrome / browsers

Implements and experiments with browser features; publishes developer guidance and tools.

MCP / AAIF

Provides an open protocol and ecosystem for connecting AI applications to external systems.

WebMCP.com

Helps people discover examples and inspect the wider public WebMCP ecosystem.

A practical example: a customer asks an AI agent to check an order. WebMCP can expose the relevant page-level action within the user's browser session. An MCP service may connect that workflow to an order-management system. The website and business service still enforce their own identity, permissions and approval rules. A directory can help developers find comparable public implementations.

HOW WE USE THESE SOURCES IN OUR TRAINING

Learn from the ecosystem. Build your own capability.

Our courses teach people to navigate the industry, understand the technical boundaries and build practical solutions. We do not present third-party documentation as our own training.

For business leaders

Understand the standards landscape, browser readiness, MCP connectivity, adoption signals, investment choices and where business value may emerge.

For product and service teams

Use real examples to identify agent-ready customer journeys, decide which actions to expose and define the customer outcome.

For developers and architects

Work from the WebMCP proposal, Chrome implementation guidance, open-source examples and MCP specifications to build and test an implementation.

For security and risk teams

Understand the trust boundaries between browser, agent, website and business systems, then design consent, authorisation, validation and evidence.

FROM INDUSTRY KNOWLEDGE TO PRACTICAL SKILLS

Know the landscape. Build what comes next.

Use the industry references to understand the moving parts, then develop the skills to make websites and business processes work with AI agents.

Explore WebMCP training