Shared capabilities. Real production.

WebMCP Mini Factory

WebMCP Unsupported ◈ 1,000 credits ☆☆☆ · 0 total
NOT A CLICK BOTThe AI operates machines, recipes and resource flows—not screen coordinates. Human controls and WebMCP tools share one FactoryEngine.

Production floor / L01

10 × 8 · deterministic simulation
Inspect a machine to see its buffers, recipe and connections. Select Conveyor, then source and destination.
⚙ Gears / min
0.0
▰ Iron plates / min
0.0
◆ Iron ore / min
0.0
▦ Circuits / min
0.0

Agent Activity

OBSERVABLE ACTIONS

Gear throughput

Live measurement

Agent Decision Trail

Actual WebMCP calls appear here. No private reasoning is displayed.

WebMCP Tool Inspector

Try asking your AI agent

CLICK TO COPY

Use a WebMCP-capable browser and agent. These prompts are copied, not sent to an external service. Unsupported browsers can use all human controls and the capability console below.

Capabilities, not coordinates

Traditional browser agent

inspect DOM ↓ find machine ↓ click machine ↓ open upgrade menu ↓ click upgrade ↓ find conveyor tool ↓ drag path ↓ inspect production UI

WebMCP agent

factory_get_bottlenecks() ↓ machine_upgrade({ machineId: "smelter-1" }) ↓ factory_get_throughput() ↓ measure and adapt

“Where is the Upgrade button?”
→ “What capability does this factory expose?”

How WebMCP powers this factory
  1. The factory exposes structured simulation capabilities.
  2. The AI agent observes actual production metrics.
  3. The agent identifies bottlenecks from resource flow and diagnostics.
  4. The agent decides how to improve capacity and spend credits.
  5. It invokes build, upgrade, recipe or conveyor tools.
  6. FactoryEngine validates and updates the shared simulation.
  7. Production changes in real time.
  8. The agent measures results and adapts.

WebMCP does not automate mouse interaction. It exposes meaningful operations on machines, recipes, connections, resources, capacity and throughput. The AI still provides observation, diagnosis, planning and optimization decisions.

The initial factory is genuinely simulated for three minutes before display, establishing a roughly 4 gears/min baseline. Rates are measured over a fixed 60-second window. Mission completion requires that rolling rate and recent production remain at target for 10 simulation seconds. Stored layouts restart their measurement window.

Belts use adjacent-cell routes, have finite transport capacity and travel time, and cannot cross. Splitters fairly alternate eligible outgoing belts. Storage holds and forwards any resource. Upgrade multipliers are 1× / 1.5× / 2× for machines and 1× / 2× / 3× for conveyors.

Natural Language ↓ AI Agent ↓ Observe → Diagnose → Plan → Act ↓ WebMCP Tools ↓ FactoryEngine ← Human Controls ↓ Shared Simulation State ↓ Production + Factory UI ↑ Observe results and adapt
Shared capability console — invoke structured tools manually
Calls the same engine. Manual invocations are logged as UI, never as an AI agent.
Select a tool to inspect its schema and run it.