WebMCP Kit

Make your website accessible to AI agents by exposing WebMCP tools they can call.

AI agents interact with websites through the UI. They parse the page, locate elements, and simulate clicks. This is slow, brittle, and breaks when the interface changes.

WebMCP is a web standard that fixes this. A page can hand the agent a small set of typed tools — search products, add to cart, book a demo — that run through the site’s own code. The agent stops guessing at your UI and starts calling functions you defined.

WebMCP Kit is a coding-agent plugin that works with Claude Code, Codex, and Cursor to add those tools to your site. It reads your codebase, proposes a short plan of tools worth having, waits for your approval, writes the code, and verifies every tool in a real browser. Tools are chosen around the journeys that matter on your site — what a visitor actually comes to do — so an agent gets the best path through your site, not a wrapper around every endpoint.

Install

/plugin marketplace add nekuda-ai/webmcp-kit
/plugin install webmcp-kit@nekuda

Using Codex or Cursor? See the Installation guide for the matching command.

Then, in your website’s repo:

/webmcp-kit:implement

Quickstart

From repo to agent-ready in one session.

How it works

The mental model: journeys, the approval gate, and what the kit will never do.

Skills

Add tools, connect existing tools, or check that they work.

TypeScript and JavaScript SDK

Install @nekuda/webmcp-sdk and add tools to React, Next.js, or JavaScript.

Verification example

Run a local example. Call a tool and check the page result.

What’s in the kit

Piece	What it does
`implement`	Add WebMCP tools to your site.
`connect-existing-tools`	Connect the tools your site already has to AgentLane.
`verify`	Check that your tools work.
Explorer	Review the plan, steer the build, and approve it in your browser.
`@nekuda/webmcp-sdk`	Add browser tools directly, or let the plugin add them. Includes TypeScript types.

The one rule that matters

Your site’s code is not changed before you approve it. The plan — which tools, wired to what, worded how — is presented to you first, and only an explicit approval moves it forward. That review gate is the product, not a formality.

WebMCP Kit is built by nekuda.