Improvisus capability network
Try Search

WebMCPify Core · Open source

Make your website usable by agents.

The local-first agent-readiness engine for new and existing applications. Discover what your product really does, expose controlled capabilities, test them in a browser, and independently verify the outcome.

Install Core View GitHub ↗
webmcpify / local
$ webmcpify discover --path ./app
✓ routes and capabilities mapped

$ webmcpify review --path ./app
○ waiting for human approval

$ webmcpify test --path ./app \\
    --url http://localhost:3000
✓ outcome independently verified

Beyond code generation

Ground every capability in the real application.

Core starts from the implementation you have: routes, forms, APIs, handlers, state and authorization. It keeps generation subordinate to review, testing and proof.

01

Repository discovery

Understands the stack, routes, forms, handlers, APIs, state stores, authentication signals and existing WebMCP registrations.

02

Grounded capability design

Drafts strict tool schemas from behavior the application actually supports; generation is one controlled step inside the workflow.

03

Human-controlled change

Uses a disposable agent workspace and an approval manifest so proposed code cannot silently reach the target project.

04

Real-browser testing

Runs approved tasks against the live site through Chrome and its experimental WebMCP inspection path.

05

Independent evaluation

Checks actual application state instead of trusting a tool or agent success message.

06

Evidence-backed repair

Connects failures to candidate repairs, retesting and durable evaluation without bypassing review.

The Core workflow

Discover → Review → Apply → Test → Verify → Repair → Evaluate

Each stage has a distinct artifact or checkpoint. Approval and independent evidence stay visible all the way through.

  1. 01

    Discover

    Map routes, forms, APIs, handlers, state, auth signals and existing tools.

  2. 02

    Review

    Inspect grounded proposals, tasks and the exact source patch before approval.

  3. 03

    Apply

    Apply only an explicitly approved patch to the target checkout.

  4. 04

    Test

    Drive the live application through a real, WebMCP-capable browser agent.

  5. 05

    Verify

    Evaluate the application’s resulting state independently of the agent’s claim.

  6. 06

    Repair

    Turn captured failures into evidence-backed proposals that require approval.

  7. 07

    Evaluate

    Preserve scores, trajectories and proof across the complete workflow.

Install and run

Local by default.
Open source by design.

The current published package is @olumide100/webmcpify. It is planned to move to webmcpify-core; the working command stays visible until that package is published.

Runtime Node.js 18 or newerBrowser Chrome with experimental WebMCP support for live testsRepository Git with an initial commit for patch review and applyOptional Temporal for durable repair and final evaluation
npm install --global @olumide100/webmcpify
webmcpify discover --path /path/to/target-project
webmcpify final-eval --path /path/to/target-project --url http://localhost:3000 --provider codex

Local MCP server

Bring Core into your coding agent.

Start the MCP server from the target repository. Its workspace boundary stays rooted there, and source changes still stop at the same review and approval workflow.

npx --package @olumide100/webmcpify webmcpify-mcp
Read the complete setup ↗

SUPPORTED PROVIDER ADAPTERS

GeminiAntigravityClaude CodeCodexOpenCode
Availability and end-to-end testing depend on the provider and local environment. Core checks browser support rather than assuming it.