Skip to main content
@mcp-b/webmcp-local-relay connects WebMCP tools running in browser tabs to desktop MCP clients such as Claude Desktop, Cursor, and Claude Code. It is the package to use when you want browser-hosted tools available in local agent workflows.

​
When to use this package

  • You want desktop MCP clients to call tools from a browser tab.
  • You want a browser-to-localhost relay instead of a DevTools bridge.
  • You are exposing site tools to external agents without requiring an extension-specific integration.

​
When not to use this package

  • You need browser automation, traces, console access, or DOM inspection. Use @mcp-b/chrome-devtools-mcp.
  • You only need in-browser discovery through a runtime or extension.

​
Where it sits in the package graph

This package is adjacent to the runtime stack rather than inside it. Pages still need to expose WebMCP tools, usually through @mcp-b/global or the embed script, and the relay forwards those tools to desktop clients.

​
First step

Start the relay in your MCP client config, then connect a browser tab that exposes WebMCP tools. The reference page documents CLI options, security controls, and the embed flow.

Reference

CLI options, architecture, security model, and embed details.

Connect desktop agents with local relay

End-to-end setup for desktop MCP clients.

Transports and bridges

Understand where the relay fits among other bridge options.

@mcp-b/global overview

Runtime setup for pages that expose tools to the relay.