--- title: Exploring WebMCP: A New Standard for AI Agent and... description: WebMCP (Web Model Context Protocol) is an emerging JavaScript API specification backed by Google and Microsoft that enables web applications to expose their... canonical: https://daily.dev/posts/exploring-webmcp-a-new-standard-for-ai-agent-and-website-interaction-qptpjqphs twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Exploring WebMCP: A New Standard for AI Agent and Website Interaction | daily.dev og:description: WebMCP (Web Model Context Protocol) is an emerging JavaScript API specification backed by Google and Microsoft that enables web applications to expose their... og:url: https://daily.dev/posts/exploring-webmcp-a-new-standard-for-ai-agent-and-website-interaction-qptpjqphs og:image: https://api.daily.dev/og/posts/QPtPJqpHS.png og:image:alt: Exploring WebMCP: A New Standard for AI Agent and Website Interaction og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Exploring WebMCP: A New Standard for AI Agent and Website Interaction **[Collections](https://daily.dev/sources/collections)** · 2 min read · 142 upvotes · 14 comments ## Summary WebMCP (Web Model Context Protocol) is an emerging JavaScript API specification backed by Google and Microsoft that enables web applications to expose their functionality to AI agents in a structured way. It introduces two APIs—a Declarative API for HTML form actions and an Imperative API for complex JavaScript interactions—allowing AI agents to interact with websites without scraping HTML or processing screenshots. Chrome offers an early preview, and the W3C Web Machine Learning Community Group has published a draft specification. WebMCP reduces token usage and resource consumption while enabling agents to collaborate with users in a shared interface, with broader rollout expected mid-year. Developers can experiment via Chrome's early preview or the MCP-B polyfill. ## Content WebMCP, or Web Model Context Protocol, is an emerging JavaScript API specification that is revolutionizing the way web applications expose their functionalities to AI agents, browser assistants, and assistive technologies. Backed by industry giants like Google and Microsoft, WebMCP allows developers to register JavaScript functions with natural language descriptions and JSON schemas, effectively transforming web pages into Model Context Protocol servers on the client side. WebMCP introduces two APIs to facilitate more reliable interactions: a Declarative API for standard HTML form actions and an Imperative API for more complex JavaScript-based interactions. These APIs allow AI agents to interact with websites without the need to scrape HTML or process screenshots, thus reducing resource consumption. Google's Chrome browser currently offers WebMCP as an early preview, showcasing its potential in real-world applications such as customer support ticket creation, e-commerce shopping flows, and travel booking. This standard not only makes it possible for agents to collaborate with users within the same interface, maintaining a shared context and user control, but also significantly reduces the cost of AI-agent interactions by minimizing token usage. The W3C Web Machine Learning Community Group published a draft specification for WebMCP, marking a significant step towards a broader rollout expected by mid-year. Developers can already start experimenting with the potential that WebMCP brings, using the early preview in Chrome or leveraging the polyfill implementation, MCP-B. In essence, by enabling structured tool exposure for AI agents, WebMCP is setting the stage for more sophisticated and seamless interactions between humans and AI in the web environment, making web applications truly AI-agent ready. ## Community discussion Top comments from developers on daily.dev. **@kevincam** · 9 upvotes > I fell like pretty soon you won't need the website. If it's just a tool for AI to get the information. Soon we'll just be building branded MCP Servers for marketing. Why worry about responsiveness, UI design, etc. For some people this will be all they need. **@fabianletsch** · 7 upvotes > What would be the motivation for a website provider to support this? Don't websites lose revenue if you do not interact with the site but just with ai tools? **@petecapecod** · 2 upvotes > This is obviously the way things are headed, it will be fun to play around with though. **@baz14** · 2 upvotes > This is the first stage of the change of the world under AI. **@japulickal** · 1 upvotes > Am I missing something? HTML is for humans, and APIs are for systems. Instead of creating WebMCP, why can’t the website owner simply create a simple MCP server? --- Tags: [#ai](https://daily.dev/tags/ai), [#webdev](https://daily.dev/tags/webdev), [#javascript](https://daily.dev/tags/javascript), [#google-chrome](https://daily.dev/tags/google-chrome) [View this post on daily.dev](https://daily.dev/posts/exploring-webmcp-a-new-standard-for-ai-agent-and-website-interaction-qptpjqphs) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Exploring WebMCP: A New Standard for AI Agent and Website Interaction","url":"https://daily.dev/posts/exploring-webmcp-a-new-standard-for-ai-agent-and-website-interaction-qptpjqphs","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/exploring-webmcp-a-new-standard-for-ai-agent-and-website-interaction-qptpjqphs"},"datePublished":"2026-02-12T14:42:12.238Z","dateModified":"2026-02-24T08:16:31.894Z","description":"WebMCP (Web Model Context Protocol) is an emerging JavaScript API specification backed by Google and Microsoft that enables web applications to expose their...","image":"https://i.ytimg.com/vi/35oWt7u2b-g/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/35oWt7u2b-g/sddefault.jpg","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":14,"discussionUrl":"https://daily.dev/posts/exploring-webmcp-a-new-standard-for-ai-agent-and-website-interaction-qptpjqphs","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":142},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":14}],"keywords":"ai,webdev,javascript,google-chrome","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"Exploring WebMCP: A New Standard for AI Agent and Website Interaction"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/exploring-webmcp-a-new-standard-for-ai-agent-and-website-interaction-qptpjqphs","comment":[{"@type":"Comment","text":"I fell like pretty soon you won’t need the website. If it’s just a tool for AI to get the information. Soon we’ll just be building branded MCP Servers for marketing. Why worry about responsiveness, UI design, etc. For some people this will be all they need.","datePublished":"2026-02-13T12:11:10.895Z","url":"https://daily.dev/posts/QPtPJqpHS#c-WB7EOow3E","author":{"@type":"Person","name":"Kevin Campbell","url":"https://daily.dev/kevincam","image":"https://lh3.googleusercontent.com/a/ACg8ocL72oVsVotdYyIluI2MUCLUuyJwkKWYXVrr9wpTwNpOcBVceCgT=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":9}},{"@type":"Comment","text":"What would be the motivation for a website provider to support this? Don’t websites lose revenue if you do not interact with the site but just with ai tools?","datePublished":"2026-02-12T15:09:42.812Z","url":"https://daily.dev/posts/QPtPJqpHS#c-M9pkX72gX","author":{"@type":"Person","name":"Fabian Letsch","url":"https://daily.dev/fabianletsch","image":"https://lh3.googleusercontent.com/a/ACg8ocKR6BVy_wn23EoOKq7-BlszlcXcLmASlnb7l-GtS-q1bePnkaJf=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":7}},{"@type":"Comment","text":"This is obviously the way things are headed, it will be fun to play around with though.","datePublished":"2026-02-18T13:19:09.253Z","url":"https://daily.dev/posts/QPtPJqpHS#c-z1rEa1yRU","author":{"@type":"Person","name":"Peter Cruckshank","url":"https://daily.dev/petecapecod","image":"https://media.daily.dev/image/upload/s--ZJhQyKws--/f_auto/v1721235024/avatars/avatar_A9xh33q0QoxtkGoJRCosp"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2}},{"@type":"Comment","text":"This is the first stage of the change of the world under AI.","datePublished":"2026-02-17T03:33:07.244Z","url":"https://daily.dev/posts/QPtPJqpHS#c-S2i6gW7lx","author":{"@type":"Person","name":"Baz","url":"https://daily.dev/baz14","image":"https://lh3.googleusercontent.com/a/ACg8ocKd2iFU8YS4sV-rBJptuYSF8EHeQnm23N_dcXE1uON7_GMIlZg=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2}},{"@type":"Comment","text":"Am I missing something? HTML is for humans, and APIs are for systems. Instead of creating WebMCP, why can’t the website owner simply create a simple MCP server?","datePublished":"2026-02-23T08:55:11.626Z","url":"https://daily.dev/posts/QPtPJqpHS#c-wxeHma4Ag","author":{"@type":"Person","name":"Jose Antony","url":"https://daily.dev/japulickal","image":"https://media.daily.dev/image/upload/f_auto/v1633664752/avatars/w0PymHPzySuODrhtzdb93"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}}]} ```