improvisus-webmcp/webmcpify-core

WebMCPify Core

Create, review, test, and verify WebMCP capabilities for new and existing web applications.

Core inspects what a site already does, asks a coding agent to draft grounded WebMCP tools in an isolated copy, and shows the exact proposal for human approval. Only an approved patch can reach the target repository. The result is tested in a real browser and checked independently of the agent's claim.

Discover → Draft → Security check → Review → Apply → Test → Verify

WebMCP and browser support are experimental. Core checks the available runtime instead of assuming support.

Install

npm install --global @improvisus/webmcpify-core

Requirements are stage-specific:

• Every command: Node.js 20.19+ on Node 20, Node.js 22.12+, or Node.js 23+.
• Generate/apply: Git with at least one target-project commit and installed target dependencies for available build checks.
• Agent-assisted commands: one authenticated Codex, Claude Code, Gemini CLI, OpenCode, or Antigravity CLI.
• Browser test/baseline: a running development or staging URL plus Chrome 150+ or a compatible Chromium build with WebMCP support.
• Durable repair/final-eval only: the optional Temporal packages, a Temporal service, and webmcpify-worker.

Core detects an installed provider when --provider is omitted. Set WEBMCPIFYPROVIDER when you want a fixed default. Core normalizes raw text, JSON envelopes, JSONL events, and nested assistant-content fields into one provider-neutral response before parsing tools and tasks. Antigravity generation runs in its edit-acceptance mode inside Core's disposable workspace. If it responds with a text-only diff, Core gives it one focused edit-only retry; no patch is created unless actual workspace source files were changed.

Browser-agent testing uses Chrome DevTools MCP. Core writes or safely merges a project-local configuration and starts its pinned package with npx; a separate global installation is not required. The first use needs registry access unless that package is already cached.

Fastest path

Start the target application, then run Core from that project's directory:

webmcpify run --url http://localhost:5173

Or select a provider explicitly:

webmcpify run --url http://localhost:5173 --provider codex

After discovery, an interactive run offers one optional product-context input. Describe workflows, existing features, or intended outcomes to help generation find relevant integrations; press Enter to skip. Discovery remains the source of truth, and Core verifies the note against the code before using it.

# Useful in a terminal; omit the option or press Enter to skip it.
webmcpify run --url http://localhost:5173 --product-context "Customers order coffee for pickup and manage subscriptions"

# Useful for scripts that must never prompt.
webmcpify run --url http://localhost:5173 --no-product-context-prompt