Toolspublished

OpenAI’s 10-Day WebMCP Challenge Pushes Websites to Expose Tools for AI Agents

The contest is an early test of whether sites will publish agent-facing actions instead of relying only on interfaces designed for human clicks.

By 3 min read
OpenAI’s 10-Day WebMCP Challenge Pushes Websites to Expose Tools for AI Agents

Listen to this story

The audio brief

About 1:31
0:001:31
Read transcript
OpenAI has opened a 10-day WebMCP challenge, offering developers cash and tools to build websites that AI agents can use through structured actions, not just clicks. The experiment is backed by Chromium, Cloudflare, Shopify, Vercel, Render, and Netlify, and it tests a bigger question: will websites publish an agent-facing set of actions alongside the interface built for people? WebMCP lets a site define named functions with descriptions and typed inputs. An agent can call those functions inside an existing browser session, where they run in the page’s JavaScript and share the user’s session. That could avoid making an agent guess its way through menus and buttons, although OpenAI’s claims that this will be faster, more accurate, and more reliable are expected benefits, not independently measured results. The scope is deliberately narrow. The current specification covers callable tools, but not the resources, prompts, or sampling features of the broader Model Context Protocol. WebMCP works in ChatGPT’s desktop browser and in ChatGPT Sites. Wider adoption is still unresolved: Chrome 146 supports it behind a developer flag, while Firefox, Safari, and Edge had not shipped implementations. Submissions close September 3, with winners planned for September 23, though that date can move. The top ten each get $3,000, a year of ChatGPT Pro, a Codex Micro keyboard, and merchandise. The key signal is whether developers find enough real web tasks to expose before browsers broadly support the standard.

Story brief

3 key points

WebMCP would let websites expose named, typed JavaScript functions that agents can call inside an existing browser session, instead of making them navigate UI elements. OpenAI is testing that model through a 10-day challenge with prizes and partners across browsers, hosting, commerce, and developer infrastructure. The experiment’s market signal is developer demand, not deployment readiness: the standard is...

  1. 01

    The current specification covers callable tools only; resources, prompts, and sampling from broader Model Context Protocol are excluded.

  2. 02

    Tools execute in webpage JavaScript and share the user’s session, avoiding a separate backend service connection.

  3. 03

    The challenge accepts submissions through September 3 and plans to announce winners September 23, though the date may shift.

OpenAI has opened a 10-day WebMCP Challenge around an experimental web standard that lets a site define structured actions an AI agent can use directly. The contest, run with Chromium, Cloudflare, Shopify, Vercel, Render and Netlify, aims to produce applications built for people and agents working together.

A more explicit contract between a site and an agent

WebMCP’s proposed shift is simple: a website can publish the functions it wants an agent to perform, rather than leaving the agent to infer a path through the site’s interface. OpenAI says that arrangement can make task completion faster, more accurate and more reliable, though those are company-stated expected benefits rather than independently measured results.

That is a different model from asking an agent to treat a page primarily as a visual workspace. It gives the site operator a role in defining the available actions, while the challenge asks developers to show that this shared human-agent design makes an application meaningfully better.

A browser-native tool surface, with a narrow first scope

The current specification is limited to callable tools: named functions with descriptions and typed input schemas. It does not yet include the resources, prompts or sampling primitives found in the broader Model Context Protocol, keeping the proposed browser surface narrower for now.

Those tools run in the webpage’s JavaScript context and share the user’s session, rather than requiring a separate backend server. That design makes WebMCP a potential interface at the point where an agent is already using a site, not a separate service connection outside the browser tab.

WebMCP is supported in the ChatGPT desktop app’s built-in browser and in ChatGPT Sites deployments. The standard is described as model-agnostic and was proposed through the W3C Web Machine Learning Community Group by engineers from Microsoft and Google, so OpenAI is adopting a proposal it does not solely control.

Adoption remains the constraint

The standard is still experimental, and browser availability is uneven. Chrome 146 has a developer trial behind its Experimental Web Platform Features flag; Firefox, Safari and Edge were participating in the W3C work but had not shipped implementations. That leaves the challenge as a test of developer interest and product design, not evidence of a settled web-wide interface.

The participation roster nevertheless puts browser, hosting, commerce and developer-platform companies around the same experiment. Challenge judges include representatives from Google Chrome, Cloudflare, Vercel, Shopify, Netlify and OpenAI, while Shopify, Google Chrome, Netlify, Cloudflare, Vercel and Render are offering additional prizes.

A short contest with a longer standards question

Registration and submissions opened August 25 at noon Pacific time and close September 3 at 1 p.m. OpenAI plans to announce winners September 23, although it says that date may move depending on submission volume.

The top 10 submissions will each receive $3,000, a year of ChatGPT Pro, a Codex Micro keyboard and OpenAI merchandise. OpenAI Developers described the total cash pool as $35,000, creating an incentive not only to prototype tools but to put them into web applications that agents and people can use together.

The useful result will not be a single winning app. It will be whether developers find enough real tasks worth exposing as structured tools to justify supporting a still-experimental browser standard across a wider set of sites and browsers.

Sources

  1. x.comOpenAI Developers (@OpenAIDevs) on X
  2. openai.comopenai.com