cf-webmcp
Connect

Connect your agent to cf-webmcp.

This page is how AI agents connect to this site via WebMCP. Once connected, your agent can call the tools listed below directly, with typed inputs and structured responses, instead of scraping pages or driving the browser visually.

Connected

This page detected WebMCP support in your browser (document.modelContext, or the deprecated navigator.modelContext alias that Chrome 146 to 149 expose). The tools below are registered with your agent and can be called directly. No pairing needed.

Pairing required

Your browser does not expose WebMCP natively. A desktop MCP client can still call this page's tools through the WebMCP bridge, a small program on your computer, and the widget on this page.

  1. Start the bridge in a terminal and leave the terminal open while you use this site's tools:
    npx -y @jason.today/webmcp@0.1.13 --foreground
    Press Ctrl+C in that terminal to stop it. The first time you run the bridge on a computer, stop it with Ctrl+C as soon as it has started and run the same command again: the first run creates the bridge's settings in ~/.webmcp but does not use them yet.
  2. Add the bridge to your MCP client, then restart the client (quit it fully and open it again). The bridge must already be running when the client starts.
    • Claude Desktop: in claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), add the webmcp entry inside mcpServers; if the file does not exist, create it with this content:
      {
        "mcpServers": {
          "webmcp": {
            "command": "npx",
            "args": [
              "-y",
              "@jason.today/webmcp@0.1.13",
              "--mcp"
            ]
          }
        }
      }
    • Cursor: the same webmcp entry inside mcpServers in ~/.cursor/mcp.json.
    • Claude Code: claude mcp add --scope user webmcp -- npx -y @jason.today/webmcp@0.1.13 --mcp
    • Other MCP clients: add a local server that runs npx -y @jason.today/webmcp@0.1.13 --mcp, where the client's documentation says.
  3. Ask your MCP client for a WebMCP pairing token, or run npx -y @jason.today/webmcp@0.1.13 --new in a second terminal.

If your client shows no tools from this site, check that the terminal from step 1 is still open, then restart the MCP client. After restarting your computer, repeat step 1 before you open the client. If step 1 says the server is already running, the bridge is running in the background; restart the MCP client.

Not connected

Your browser does not expose WebMCP, and the fallback widget for desktop MCP clients is disabled on this site. You cannot pair from here right now.

Chrome ships WebMCP to users through an origin trial (from Chrome 149) on sites that send a trial token. To test without a token, turn on chrome://flags/#enable-webmcp-testing and relaunch. Cloudflare's Kitesurf agent browser also supports WebMCP. See browser support for the current state. If you are the site owner, set fallback_widget = true in webmcp.toml, pin and upload the widget (npm run update-widget, then npm run upload-widget) and redeploy to enable the desktop pairing flow.

Tools available


About WebMCP

WebMCP is a way for websites to expose structured tools that AI agents can call. There are two runtimes behind the same name, and they reach different agents.

This site uses cf-webmcp to expose both surfaces from a single config.

Configuration hash: 635e2730

Diagnostic: what this page detected