Skip to content
WebMCP Kit
Esc
↑↓navigate↵open⌘Jpreview
On this page

/webmcp-kit:connect-existing-tools

Connect the tools your site already has to AgentLane.

Connect your existing WebMCP tools to AgentLane. Review the changes first. Your tools keep working as before.

/webmcp-kit:connect-existing-tools

Run it in your site’s repo. You can also pass a workspace path or site URL. The skill needs the source code to change how tools are registered.

When to use it

  • Your site already has WebMCP tools and you want to see them and their activity in AgentLane.
  • Your tools use the native browser API and you want to move their registration onto the SDK.
  • Your tools already use @nekuda/webmcp-sdk and only need connecting.

No tools yet? Use implement to build them.

What changes

The skill moves tool registration onto @nekuda/webmcp-sdk where needed. It keeps each tool’s name, inputs, code, page effects, and availability the same. Existing stableKey values stay unchanged.

Before editing, it shows which tools can be migrated, which are already ready, which need manual work, and every file that will change. You approve that plan first.

Native WebMCP tools and this SDK are supported, including its older package names. Tools using another SDK, or whose source cannot be found, are listed as needs manual migration.

Connection and checks

After migration, you can connect to AgentLane or skip for now. Skipping leaves the tools migrated and working, but unconnected.

The skill compares the tools before and after the change, checks their behavior in the browser, and confirms a real tool call appears under your account. Anything it cannot verify is stated in the report.

The work lands on a webmcp/connect-existing-tools branch. The PR includes the plan and results for each tool.

The SDK sends limited anonymous usage data by default. Connecting links activity to your account. See Privacy for details and controls.

Headless runs

Use --non-interactive to proceed on stated defaults without the approval step. This mode skips the AgentLane connection and records its assumptions in the report. Without that explicit request, the skill waits for your approval.

Was this page helpful?