WebMCP Generator

What the WebMCP Generator creates

The Generator turns a discovered or manually described website action into a reviewable implementation starting point. It creates a stable tool name, human-readable description, JSON Schema input contract, risk annotations, an explicit confirmation boundary for consequential actions, and a fallback path for browsers that do not expose the API. It is intentionally a code scaffold, not a deploy button: selectors, authentication, server routes, authorization and business rules must be connected to the real application.

Start from a scan or a known action

Run a public URL through the Autopilot or Checker when the workflow is visible in HTML. If the action is behind login, rendered only after interaction, or known from product documentation, use the manual form on this page. Describe the user goal, not the name of a framework hook: “search products”, “prepare a quote”, or “request an appointment” leads to a clearer contract than “submit form 2”.

Practical input and output example

For a product lookup, an input can be a query plus constraints. A useful contract might contain {"query":"black laptop","maxPrice":900,"currency":"EUR"}, with required types, ranges and descriptions. The generated output is a document.modelContext.registerTool() skeleton whose execute handler receives that object, validates it again, calls an existing authorized endpoint and returns a structured result. For a quote, use product, quantity and optional requirements; for booking, use date, time, name and email. Do not invent fields that the application cannot actually honor.

Current syntax and safe boundaries

The current documented imperative surface is document.modelContext. The generated code feature-detects that surface and keeps a human-facing fallback. It may include readOnlyHint, consequentialHint and untrustedContentHint annotations, but annotations do not replace server-side controls. Never put credentials or secrets into a tool. A booking, MFA reset, checkout, payment, order or external submission must show the final values and require human confirmation immediately before the commit.

Review the generated code before use

Replace the example endpoint, connect the real validation library, map errors into useful messages, enforce authorization on the server and test duplicate registration after navigation. Check idempotency for retries and make cancellation safe. Keep labels, consent, keyboard access, loading, error and success states in the visible form. Use the Validator for static review and the Simulator to check whether the tool matches real tasks.

From scaffold to implementation

The Generator is most useful when it shortens the gap between an SEO or product discovery result and an engineering ticket. Save the schema with the action owner, expected response shape, risk decision and test cases. Then involve the WebMCP Implementation Service when the workflow touches customer data, identity, money or regulated records. A generated file is not a verification result; only a controlled browser and application test can justify a Verified label.