Disposable workspaces
Generation agents never edit the target checkout directly.
WEBMCP-NATIVE · HUMAN-APPROVED
Make every app agent-ready.
WebMCPify helps people and coding agents turn real application capabilities into reliable tools — without giving up control of the code.
⌁ A WebMCP-enabled browser agent can use this page’s tools.
✓
This homepage was made agent-ready with WebMCPifyDiscover → generate → review → verify
{
"project": "your-app",
"capabilities": ["forms", "state-management", "existing-webmcp"],
"next": "human review"
}✦ WebMCP tools found4 ready for an agent
Built for the agent-native webDISCOVER REAL CAPABILITIESHUMAN APPROVAL REQUIREDVERIFY WITH EVIDENCE
01 / THE IDEA
Agents should understand your app before they touch it.
Most agents see a screen and guess. WebMCPify gives them a grounded path: inspect the app, draft tools from what is really there, and let a person decide what gets applied.
This homepage is the proof: it was built as a normal Next.js project, then made WebMCP-ready with WebMCPify’s human-approved workflow.
It works with a brand-new project, an existing site, or a site that already has WebMCP integrations.
02 / THE WORKFLOW
From codebase to capability.
● WEBMCP TOOLS LOADING03 / SAFETY + EVIDENCE
Useful for agents.
Safe for people.
WebMCPify treats every source change as a permission boundary. Patches are inspectable, repair needs approval again, and the final result is independently checked.
Approved patches
Git fingerprints, paths, approval IDs, builds, and rollback protect apply.
Human repair loop
A failed task creates a proposed repair; a person must approve it.
Independent proof
Browser state and verification expressions—not agent claims—decide success.
04 / WEBMCP-NATIVE PAGE
This page is agent-readable.
In a WebMCP-enabled browser, an agent can discover and invoke these tools directly from the page. They are registered with the native document.modelContext API, not simulated buttons or a separate backend MCP server. The implementation follows the official WebMCP specification ↗.
● ENABLE WEBMCP IN YOUR BROWSER TO EXPOSE THESE TOOLS
Open this deployed page in ChatGPT’s in-app browser or Chrome with WebMCP enabled, then ask the agent to explain WebMCPify or show the Review step.
WebMCPify source repository
Agents and humans can get the CLI, MCP adapter, prompts, evaluators, Temporal worker, browser launcher, and demo from the WebMCPify GitHub repository ↗.
explain_webmcpify
Explain the product and human + agent workflow.
document.modelContext.registerTool()show_workflow_step
Highlight any step in the full workflow.
document.modelContext.registerTool()get_webmcpify_setup
Return CLI, MCP, browser, and Temporal commands.
document.modelContext.registerTool()get_webmcpify_safety_model
Explain approvals, patches, isolation, rollback, and evidence.
document.modelContext.registerTool()04 / START BUILDING
Your app has capabilities. Make them available.
Use the CLI yourself, or let a coding agent work through WebMCPify with your approval.
$ cd /path/to/WebMCPify$ pnpm install && pnpm build$ cd /path/to/target-project$ git init && git add -A && git commit -m "Initial target snapshot"$ pnpm install && pnpm dev --host 127.0.0.1
Human-led setup
Use the same TARGET_URL for Chrome, baseline, test, repair, and final evaluation. For a deployed app, skip the target-app terminal.
Terminal 1: target app. Terminal 2: pnpm chrome:headless TARGET_URL. Terminal 3: temporal server start-dev. Terminal 4: pnpm build && pnpm temporal:worker. Terminal 5: run the CLI from WebMCPify.
pnpm webmcpify final-eval --path /path/to/target-project --url TARGET_URL --provider codexFinal evaluation performs discovery, generation, human review, baseline, approved apply, WebMCP testing, permissioned repair, and Temporal evaluation.
CLI, npm, and MCP
pnpm webmcpify discover --path /path/to/target-project
pnpm webmcpify generate --path /path/to/target-project --provider codex --method auto
pnpm webmcpify review --path /path/to/target-project --port 4173
pnpm webmcpify apply --path /path/to/target-project
pnpm webmcpify test --path /path/to/target-project --url TARGET_URL --provider codex
pnpm webmcpify repair --path /path/to/target-project --url TARGET_URL --task task-1 --provider codex --durable
npm install --global @olumide100/webmcpify
cd /path/to/target-project && npx --package @olumide100/webmcpify webmcpify-mcpTemporal is required for final-eval and durable repair. Human approval is required before the initial patch and every repair patch.