WebMCP

Procedures

Step 1: Identify the browser integration surface

Inspect the workspace for browser entry points, UI handlers, and any existing app state or form handling layer.
Execute node scripts/find-webmcp-targets.mjs . to inventory likely frontend files and existing WebMCP markers when a Node runtime is available.
If a Node runtime is unavailable, inspect the nearest package.json, HTML entry point, and framework bootstrap files manually to identify the browser app boundary.
If the workspace contains multiple frontend apps, prefer the app that contains the active route, component, or user-requested feature surface.
If the inventory still leaves multiple plausible frontend targets, stop and ask the user which app should receive the WebMCP integration.
If the project is not a browser web app, stop and explain that this skill does not apply.