WebMCP experiment · capability factory

Software that can invent new tools for its own agent.

Capability Foundry begins with five generic WebMCP primitives. Use them to create data objects, rules, views, and workflows — then publish the workflow as a brand-new live WebMCP tool. The application literally expands the agent's capability surface at runtime.

01 · Describe the outcome

Mission

The preset demonstrates the self-extension loop. An external agent can accomplish the same thing by calling the five primitive WebMCP tools.

02 · Watch software assemble itself

Capability pipeline

Every stage is implemented by the same application logic exposed to agents through WebMCP.

1ObjectDefine the thing the workflow operates on.

2RulesEncode deterministic policy and routing.

3ViewCreate a human-facing cockpit for the capability.

4WorkflowCompose steps and rules into reusable behavior.

5PublishRegister a brand-new live WebMCP tool.

03 · Generated application

Artifacts

The agent isn't just filling in fields; it is manufacturing persistent application structure.

No generated artifacts yet.

04 · Use the thing it created

Generated capability runner

When a workflow is published, this runner is generated from the same parameter schema registered with WebMCP.

Publish a workflow to generate a runnable capability.

Live agent surface

Tool registry

Pink entries are capabilities created while the page is running.

Runtime evidence

Event stream

Watch registrations, executions, artifacts, and WebMCP toolchange events.

Test with an agent

Agent handoff

Use this page's WebMCP tools to satisfy the mission. Do not merely describe a workflow. Create the object, approval rules, a useful view, the workflow, then publish it as review_vendor_invoice. After publishing, call the new capability with an invoice amount of 127500 to prove the new tool works.

The page uses the current document.modelContext.registerTool() API when available, with AbortController-owned registrations so generated tools can be removed cleanly. A legacy navigator alias is accepted only as a compatibility fallback.