WebMCP Playground

Execute tools by hand in the inspector, or press Simulate agent traffic to fire a burst of calls the way an agent would. Everything lands in analytics on the right. The quickest thing to try is generate_placeholder_text, which comes from the placeholder block at the bottom of this page.

Inspector <machvive-webmcp-inspect>

Analytics <machvive-webmcp-analytics>

Products from JSON-LD <machvive-webmcp-products>

This page carries ordinary schema.org Product markup — the same JSON-LD a site already publishes so search engines understand its catalogue. The component reads it and exposes search_products, get_product and list_product_facets. Nothing was written by hand, and there is no backend.

Look at search_products in the inspector: its category and brand fields are dropdowns, because the allowed values were derived from this page's own data. An agent never has to guess a category name. The tools are read-only — they search and read, never add to a cart.

Placeholder copy <machvive-lorum-ipsum>

This element publishes generate_placeholder_text by simply being on the page — no tool written by hand. Find it in the inspector above, choose a language, set a sentence count, and run it. The copy below changes. That is the whole WebMCP loop: an agent calls a named, schema-typed function, and your page does something.