Quickstart

Run your dev server as usual — npm run dev, bun dev, whatever your repo uses. The plugin verifies tools against the running site later.

Open the repo in Claude Code, Codex, or Cursor and run the implementation skill: /webmcp-kit:implement in Claude Code or Codex, or /implement in Cursor.

It reads your routes, forms, and data layer to figure out what a visitor comes to this site to do. Nothing is written yet — this phase is read-only.

You get a short plan in the Explorer: each proposed tool with its name, its exact description, and what it will be wired to. Anything the plugin wasn’t sure about is a question with a stated default, not a guess.

Edit freely — rename tools, drop tools, reword descriptions. It proceeds only on an explicit approval. Prefer chat? Add --no-interactive-loop when you run the skill.

After approval it adds the SDK, writes the tool modules in your repo’s own style, then verifies: type checks, site still boots, each tool registers on the right pages and works when called. Every tool ends verified, failed (fixed or dropped — never shipped), or could-not-verify (shipped, flagged).

See your registered tools and their activity in AgentLane. Choose Connect to AgentLane or Skip for now. Your tools work either way.

The work lands on a webmcp/tools-v0 branch with a PR whose body is the approved plan plus the per-tool verification table.