MetaWebMCP observes the parts of a site an agent can safely use, turns them into bounded semantic recipes, and exposes those recipes as simple tools—without waiting for the site to ship native WebMCP.
Open a public site in the workspace, watch the recipe run, or export and integrate it into a site you own.
find_sessions
find_sessions({ query })A website does not need complete native coverage to become useful to an agent. MetaWebMCP finds the safe, observable portion and gives it a stable semantic shape.
Enter a public URL. The workspace shows both the rendered page and the accessibility model used to derive tools.
Turn accessible controls into a small tool with a clear name, schema, evidence, risk, and deterministic browser steps.
Add the recipe to the live tool registry, let the agent invoke it by intent, and verify the visible result before export.
Use the workspace’s visible isolated session, or let a calling agent retain an authorized browser session. Either way, the generated tool provides a validated recipe with bounded targets, inputs, and expected results.
Export a standalone repository with the reviewed ToolSpecs and direct document.modelContext.registerTool(...) calls. Integrate them as-is, or bind the contracts to your application functions and permission checks.
MetaWebMCP omits ambiguous or inaccessible controls, keeps consequential actions behind review and confirmation, and never weakens the access already enforced by the target website.
Enter a public URL. MetaWebMCP opens it in an isolated browser and keeps the page, accessibility model, recipes, and results together here.
Checking the isolated browser runtime.
Enter a public URL and inspect it. You will be able to see the rendered page and the accessibility model used to derive tools.
Observe the real UI, shape narrow tools, prepare or run them, then ship the same contracts as native code.
ChatGPT Site Tools: Open this URL as a top-level page in the latest ChatGPT desktop app’s built-in browser. Use ChatGPT Work or Codex with GPT‑5.6 Sol or Terra. Site Tools are disabled on Luna, unavailable in Enterprise and Edu, and may not yet be enabled in every eligible workspace.
Google Chrome 149 or later: Open chrome://flags/#enable-webmcp-testing, enable the WebMCP testing flag, and restart Chrome. Then open this URL as a top-level page. A working native setup shows WebMCP active and seven meta-tools.
Agent-controlled browser fallback: If the Cloudflare-hosted viewer is rate-limited or cannot render the target, have the agent open the page with its browser, capture the accessibility snapshot, and call meta_analyze_site with source: "agent_snapshot". Generated browser tools return bounded plans for that agent to execute and verify.
The numbered controls call the same implementations as the seven registered meta-tools.