From website
to agent-ready.
Build tools and then see how agents use them.
A live directory of websites exposing WebMCP tools to AI agents. Browse the tools each site registers, inspect their input schemas, or query the agent-readable JSON API. Built on the W3C webmachinelearning/webmcp proposal and maintained by nekuda.
Explore agent-ready sites. Build and improve your WebMCP tools.
nekuda platform
Free tier: 1 website · 10,000 tool calls/month
ConnectWe’ll scan your WebMCP tools and email you the report.
Sites with WebMCP tools are reviewed before listing.
↻ Shipped new tools? You can always rescan.
Shopify stores share the same WebMCP implementation. Explore the shared tools below, or find a store.
2,375,833 stores in the Shopify index.
Agents can now complete checkout on every Stripe-hosted checkout page, powering more than 7.8 million businesses.
Tools captured live from a Stripe-hosted checkout.
Tools as JSON · Stripe's WebMCP guide · Official discovery example
WebMCP is a proposed web standard that lets a website give AI agents a list of actions they can use directly, like searching products, booking a table or filling in a form. Instead of trying to click buttons and figure out a page like a human, the agent uses the actions the website provides.
Engineers from Google and Microsoft are developing it in the W3C’s Web Machine Learning Community Group. Each action is a tool with a name, a description and the inputs it needs. A site can turn an existing HTML form into a tool with a few attributes, or register a JavaScript function through the browser’s document.modelContext API.
There are two main ways people use it. In co-browsing, you and an AI assistant work on the same page in your browser. ChatGPT’s desktop app already does this with WebMCP tools. Gemini in Chrome is the same kind of assistant, but it can’t use WebMCP tools yet. In remote browsing, an AI app opens its own browser and completes the task for you, with or without you watching.
Because the website tells the agent exactly what it can do, tasks are faster, more reliable and more predictable than screen scraping. webmcp.com lists 6,446 websites that already support WebMCP.
Give agents tools instead of making them guess. With WebMCP, your site tells an AI agent exactly what it can do, like search, add to cart or book. ChatGPT’s desktop app already uses these tools in its built-in browser.
There are two ways to add them. If your site uses plain HTML forms, give each form a name and a description with the toolname and tooldescription attributes, and the browser turns it into a tool. For anything a form can’t do, register a JavaScript function with document.modelContext.registerTool().
Use “Build WebMCP tools for your website” at the top of webmcp.com. Copy the setup prompt into your coding agent to build and test tools with Google’s WebMCP skills. You can also include the optional connection to the nekuda platform, or uncheck it to build tools only.
As of October 2026, ChatGPT is the main AI assistant that uses WebMCP tools: its desktop app has done so in its built-in browser since August 25, 2026. Brave’s assistant, Leo, can use them in Brave Nightly behind a flag. Gemini in Chrome can’t use WebMCP tools yet, and Claude for Chrome doesn’t use them.
Chrome and Edge are testing WebMCP in an origin trial, Brave has it behind a flag, and Firefox and Safari have no implementation. Developer tools like Stagehand and Vercel’s agent-browser already support it.
MCP connects an AI app to servers and services somewhere else; you can think of it as an API for AI. WebMCP lets the web page itself hand tools to the AI agent that’s using it, in the browser and inside the user’s own session. llms.txt is a text file that helps AI read your site, while WebMCP lets AI use it.
The stated goal of the WebMCP proposal is co-browsing, where users stay on a website and work with it alongside their AI assistant, rather than the AI operating in a separate application. In many cases, this is better for everyone. Users can get through complex interfaces more easily while staying in control, and website owners keep users engaged on their own site instead of moving the experience into a headless browser.
WebMCP can also be used from remote automated browsers. Website owners can block that kind of access with their existing bot protection or other access controls.
Yes, if your site gives them tools for it. With WebMCP, an agent can search, fill a cart or start a booking by calling actions your site defines. Anything that spends money or makes a commitment should ask the person to confirm first.
Shopify and Stripe already have this built in. Shopify stores share WebMCP tools for search, products and the cart, plus checkout tools that place an order only after the buyer confirms; we track more than 2.3 million Shopify stores. Stripe Checkout has its own WebMCP tools for paying. Other sites add their own tools, and the webmcp.com directory shows how shops and travel sites do it.
Use the directory’s listing check to scan for WebMCP tools on your live website. Enter your website and report email, then press “Scan live tools”. This checks existing tools; it does not build new ones.
The scan lists the tools it finds and grades their implementation. It also requests a directory listing or update for review. A scan or listing does not prove that an agent can complete every customer task; test those tasks separately.
Use “Get more from your WebMCP tools” at the top of webmcp.com, then choose “Connect” to open the nekuda platform. Sign in there and follow the platform’s onboarding to connect your project.
Once connected, you can monitor agent activity, investigate failures, build tools, and create WebMCP workflows.
Query the directory programmatically — list sites, inspect each tool's
input schema, probe a URL with /api/v1/lookup, or pull
aggregate counts. Read-only JSON, no auth, CORS open. Stub-only sites
(modelContext present but no registered tools) are
excluded.
OpenAPI 3.1 spec at /api/openapi.json · full reference at /api-docs