Specification · Chrome Labs · community

Official WebMCP sources

These are the public spec and demo surfaces the evaluator is written against. They are not our product. Running evaluate_webmcp against them is optional and billed like any other public URL.

Tools work best when they encode user goals, not UI widgets. Agents then pick one high-level action instead of reconstructing a click path. That is why WebMCP setups on the open WindTunnel board solved 49/49 tasks while the same models on raw DOM often stalled.

Chrome Labs utilities and demos

Hub: github.com/GoogleChromeLabs/webmcp-tools. Interactive pages live under /demos/ on GitHub Pages.

• Le Petit Bistro — declarative form tools (toolname / tooldescription).
• React Flight Search — imperative tools in a SPA.
• zaMaker pizza — configurator.
• Mystery Doors — mixed declarative + imperative, multi-page.
• CineFlow — showtimes and checkout-adjacent flow (we still refuse pay tools).
• L'Atelier hotel — booking answers, not silent writes to a calendar.
• Morning Ritual — boutique catalog (low-volume B2C analogue).
• Smart Home — dashboard / app layout tools.

Chrome Labs also ships a Model Context inspector extension and a CLI named webmcp-evals. That CLI is not this evaluator (https://mcp.webmcp-eval.com/mcp).

Community list

Awesome WebMCP (W3C Web Machine Learning Community Group) collects articles, frameworks, live sites, and talks. Labs keeps a shorter demo list in AWESOME_WEBMCP.md.

After you have seen a demo, connect the evaluator and run it on the client URL you actually own.