webmcpify

Exposes web app functionality as WebMCP tools through an inventory, integration, and browser verification pipeline.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill webmcpify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webmcpify
Source: https://github.com/github/awesome-copilot/tree/main/skills/webmcpify
Command: npx skills add https://github.com/github/awesome-copilot --skill webmcpify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Browser AI agents currently interact with web apps by guessing at the DOM, which is fragile and error-prone. This Skill makes an existing web application agent-ready by exposing its user-facing actions as structured WebMCP tools (document.modelContext), with a human approval gate and real-browser verification so nothing ships unproven.

Core Features & Use Cases

  • Phased pipeline with human gate: Runs DETECT, INVENTORY, INTEGRATE, VERIFY, HEAL, and AUDIT phases, pausing at a manifest approval gate where you approve or reject each proposed tool before any code changes.
  • Declarative and imperative integration: Annotates standard HTML forms with toolname/tooldescription attributes, or registers imperative tools via a vendored, dependency-free runtime that wraps the app's existing UI code paths.
  • Real-browser verification and self-healing: Generates Playwright specs that run in headed Chrome against the production WebMCP surface, then diagnoses and fixes failures with a bounded heal loop.
  • Use Case: Point it at a React SaaS app and say "webmcpify the tickets area" — it maps user actions into a tool manifest, gets your approval, integrates the tools without touching unrelated code, and proves each one works in a real browser.

Quick Start

Run the webmcpify skill on this repository to inventory user-facing actions and expose them as WebMCP tools.

Frequently Asked Questions about webmcpify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make my web app accessible to AI agents with WebMCP?

Run the webmcpify pipeline: it inventories user actions into a tool manifest, gets your approval at a gate, then integrates tools via declarative form attributes or imperative registerTool calls. Verification runs in real headed Chrome to prove each tool works.

What is the difference between declarative and imperative WebMCP tools?

Declarative tools annotate existing HTML forms with toolname and tooldescription attributes, letting the browser derive the schema. Imperative tools use document.modelContext.registerTool for non-form actions, controlled React forms, or state-driven inputs.

Does WebMCP work in browsers other than Chrome?

WebMCP is currently a Chrome origin trial incubated in the W3C Web Machine Learning Community Group. The integration is fully feature-detected, so the app behaves identically in browsers without WebMCP support.

Why does WebMCP verification fail in headless Chrome?

WebMCP requires a visible tab by design, so headless mode will never work. Run Playwright with a headed persistent Chrome context and the --enable-features=WebMCP,WebMCPTesting flag, using xvfb-run in CI environments.

Can webmcpify modify unrelated code in my repository?

No. A ground rule enforces zero unrelated changes: every diff hunk must trace to a manifest entry or recorded setup step, files dirty at baseline are untouchable, and a final audit flags any unmapped change without reverting it.

When should I not use WebMCP for agent integration?

Do not use it for backend-only MCP servers (that is classic MCP), automating third-party sites you do not control, or exposing destructive, irreversible, or payment actions in a first integration.