Browser-native capabilities · interactive kitchen

WebMCP Pizza / Burger Builder

Build food through UI or AI tools.

Checking WebMCP… One state. Two ways to build.

Your creation

LIVE PREVIEW
Made of state, not clicks

Configuration
Toppings
Per item
A shared capability layer. Human controls and AI tools call the same BuilderEngine. No DOM automation.

Make it yours

DRAFTS AUTO-PRESERVED

Activity Log

A transparent audit trail · UI, WebMCP, and System · newest first

Last AI action: waiting for an agent.

WebMCP Tool Inspector

Structured capabilities · expand a tool to inspect its schema

Try asking your AI agent

Click to copy

Use these in a WebMCP-capable agent connected to this page. These buttons copy prompts; they do not simulate an AI.

How WebMCP works

  1. The page exposes structured food-building tools.
  2. An AI agent discovers those tools.
  3. The agent calls them with structured arguments.
  4. The shared BuilderEngine updates application state.
  5. The UI immediately reflects the same state.

Tools describe intent: pizza_add_topping({topping: "mushroom"}), not coordinates or selectors. Validation, pricing, undo, and rendering are identical for human and agent actions.

Everything runs locally in this tab. Orders are demo confirmations only. No server, payments, remote API, or network connection is required for the builder. Drafts last for this page session.

AI Agent ↓ WebMCP Tools ↓
Human UI ↓
BuilderEngine · validate / mutate / undo ↓ Application State · one source of truth ↓ Food UI · preview + price + summary