Build with a coding agent
Build full WebMCP tools with the coding agent you already use.
claude plugin marketplace add nekuda-ai/webmcp-kit && claude plugin install webmcp-kit@nekuda
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.
Browse websites agents can use.
Scan your WebMCP implementation.
Build full WebMCP tools with the coding agent you already use.
claude plugin marketplace add nekuda-ai/webmcp-kit && claude plugin install webmcp-kit@nekuda
Our scanner reads your website and suggests the right WebMCP tools for it — implement one snippet of code to go live.
↻ Shipped new tools? You can always rescan.
Shopify stores share the same WebMCP implementation. Explore the shared tools below, or find a store.
833,707 stores in the Shopify index.
Agents can now complete checkout on every Stripe-hosted checkout page, powering more than 7.8 million businesses.
Tools as JSON · Stripe's WebMCP guide · Official discovery example
WebMCP lets websites give AI agents a direct way to interact with them. Instead of trying to click buttons and figure out a page like a human, AI can use actions the website provides.
There are two main ways people use WebMCP. The first is co-browsing, where you interact with AI built into your browser, such as Gemini in Chrome. The second is remote browsing, where AI applications like ChatGPT or Claude open a browser and complete tasks on your behalf, with or without you watching. Both ChatGPT and Claude have recently added browser support.
Because websites tell AI exactly what they can do, interactions become faster, more reliable, and more predictable than screen scraping. webmcp.com is a live directory of websites that support WebMCP.
MCP connects AI applications to servers and services. You can think of it as an API that lets AI access capabilities outside the application itself.
WebMCP brings that idea into the browser. The stated goal of the WebMCP proposal is to enable co-browsing, where users stay on a website and interact 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 navigate 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. However, website owners can choose to block remote automated browser access using existing bot protection or other access controls.
Ship WebMCP tools on your site, then submit it through the “Add your site” box on webmcp.com. Our scanner verifies the tools are live before listing.
Yes. Curated directory records are available as JSON at /api/v1/sites and /api/v1/sites/<host>. Shopify stores have a separate index: read shared tools at /api/v1/platforms/shopify and search stores at /api/v1/platforms/shopify/stores?q=. The OpenAPI spec is at /api/openapi.json. See the API for Agents page.
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