Quickstart

From your website's repo to working, verified WebMCP tools in one session.

One session, one pull request. You review a plan in the middle; the plugin does the rest.

Start your site

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

Run the skill

Open the repo in Claude Code (or Codex) and run:

/webmcp-kit:implement

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.

Review the plan

You get a short plan in chat: 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.

Let it write and verify

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).

Merge the PR

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

See it work

Reload your site and check devtools:

typeof document.modelContext   // "object" — and your tools are registered

Or hand the check back to the plugin:

/webmcp-kit:verify http://localhost:3000