Agent skill · software engineering · github
webmcpify
Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for "webmcpify", "add WebMCP", or "expose app actions to AI agents".
Why this skill is useful
Adds a complete executable pipeline for integrating WebMCP tools into web applications, enabling AI agents to interact with the app's functionality directly.
What it needs
Requires node installed locally. About 10k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
webmcpify — make any web app agent-ready, verifiably You are running the webmcpify pipeline. It takes an existing web application and exposes its user-facing functionality as WebMCP tools (document.modelContext — a proposed web standard incubated in the W3C Web Machine Learning Community Group, currently a Chrome origin trial), so browser AI agents can operate the app through structured tool calls instead of guessing at the DOM. Everything you need ships inside this skill directory: phase guides in references/, and vendorable code in templates/ (runtime, ambient types, JS variant, React JSX typings, verification spec). Never assume files exist outside the skill dir. Out of scope (stop and say so): backend-only MCP servers (that's classic MCP, not WebMCP), automating third-party sites you don't control, and generic SEO work. Invocation modes The user may pass an argument (/webmcpify <mode> or plain words): Argument Run Stop at --- --- --- (none) or full all phases, resuming from current manifest state done inventory / map DETECT + INVENTORY loops only — zero code changes present the manifest table for review integrate INTEGRATE loop only (requires approved tools in the manifest) integrated + built verify VERIFY + HEAL loops on integrated/verified tools green/skipped report status read .webmcpify/manifest.json — read-only report phase, per-status tool counts, and the recommended next command Any other text is scoping guidance (e.g. "only the checkout area", "read-only tools only"). Ground rules (non-negotiable, enforce in every phase) 1. Zero unrelated changes. Every diff hunk you produce must trace to a manifest entry or the recorded one-time setup. Never refactor, reformat, rename, or "improve" anything else — note problems in the report instead. Files that were already dirty at baseline (recorded in the manifest) are untouchable: never modify or revert them. 2. Read-only tools first. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/webmcpify