Use TabPilot with Claude Desktop and other MCP clients

TabPilot runs an MCP server on your Mac at http://127.0.0.1:47823/mcp (Streamable HTTP, with a Bearer token). Claude Desktop’s config file only starts local programs, so it reaches that server through a bridge: "command": "npx", "args": ["-y", "mcp-remote", "http://127.0.0.1:47823/mcp", "--header", "Authorization:Bearer <token>"]. That needs Node.js. Clients that support Streamable HTTP connect to the URL directly with the header Authorization: Bearer <token>. The TabPilot app shows both, with your token filled in.

Updated

What every client needs to know

TabPilot is a Mac app plus a Safari extension. The app runs a small MCP server; the extension carries out what the agent asks inside Safari. Any MCP client needs three things to connect:

  • The address: http://127.0.0.1:47823/mcp. 127.0.0.1 means this Mac, and 47823 is TabPilot’s port.
  • The transport: Streamable HTTP, the MCP transport for servers you reach by URL.
  • The token: sent as the header Authorization: Bearer <token>. The app shows it under Connect an agent. Requests without it are refused.

The TabPilot app must be open while you use it, and the extension must be on in Safari › Settings › Extensions. If you use Claude Code, it connects over HTTP directly; see how to connect Claude Code to Safari.

Claude Desktop, through mcp-remote

Claude Desktop reads its MCP servers from a config file, and each entry there is a local program to start: a command with args. TabPilot isn’t a program to start; it’s a server that is already running. The bridge between the two is mcp-remote: Claude Desktop starts it with npx, and it forwards everything to TabPilot’s URL with your token. This is the entry the app gives you:

{
  "mcpServers": {
    "tabpilot": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "http://127.0.0.1:47823/mcp", "--header", "Authorization:Bearer <token>"]
    }
  }
}

Copy it from the app exactly as shown. Note that the header is written Authorization:Bearer <token>, with no space after the colon.

  1. The bridge runs with npx, which comes with Node.js. If npx --version in Terminal prints a version, you already have it; otherwise install Node.js first.
  2. In the TabPilot app, under Connect an agent, choose Claude Desktop and click Copy. The entry already contains your token.
  3. It is claude_desktop_config.json, in ~/Library/Application Support/Claude/ on a Mac.
  4. Paste the tabpilot entry inside "mcpServers". If the file already lists other servers, add it next to them, separated by a comma, so the file stays valid JSON.
  5. Quit Claude Desktop completely and open it again, so it starts the bridge.
  6. Ask Claude something like “Use tabpilot to check the status of the Safari extension.” It should call the tabpilot_status tool.

npx -y downloads mcp-remote the first time and runs it without asking. If you’d rather check a package before running it, look it up on npm first; the bridge only needs to reach 127.0.0.1.

Clients that speak Streamable HTTP

Many MCP clients can add a server by URL. For those, no bridge and no Node.js are needed. Use these values, from the app’s Other tab:

URL:     http://127.0.0.1:47823/mcp   (Streamable HTTP)
Header:  Authorization: Bearer <token>

Where your client asks for the server type or transport, choose Streamable HTTP (sometimes just “HTTP”). Where it asks for headers, add one named Authorization with the value Bearer, a space, and your token. Give the server a short name such as tabpilot.

The exact screens and file formats differ from client to client, and they change between versions, so follow your client’s own documentation for “adding a remote MCP server” or “adding an HTTP MCP server with headers”. Codex and other agents work as long as they support MCP over HTTP with a custom header.

Clients that only start programs

Some clients, like Claude Desktop, only know how to start a local program and talk to it over standard input and output (stdio). For them, use the same idea as for Claude Desktop: a server entry whose command is npx with the arguments -y, mcp-remote, the URL, --header and Authorization:Bearer <token>. Node.js has to be installed.

Keep the token safe

The token is what stops other programs from controlling your Safari through TabPilot. It works only on this Mac, but treat it like a password:

  • Don’t commit config files that contain it to a Git repository, and don’t paste it into chats or shared notes.
  • If it might have leaked, click New Token… in the app. Every setup with the old token stops working at once; copy the new entry into each client.
  • Give the agent only the access it needs in Site Access. The token lets a client talk to TabPilot; Site Access and the approval prompts still decide what it may do in Safari.

If it doesn’t connect

  • Connection refused: the TabPilot app isn’t running. Open it.
  • 403 Forbidden: the token is wrong or old. Copy the current entry from the app again, especially after New Token….
  • Claude Desktop shows no TabPilot tools: check that claude_desktop_config.json is valid JSON, that npx works in Terminal, and that you restarted Claude Desktop.
  • “The Safari extension is not connected”: the client reached TabPilot, but Safari didn’t. Turn the extension on in Safari › Settings › Extensions.
  • The client runs somewhere else (another Mac, a virtual machine, a container): it can’t reach 127.0.0.1 on this Mac. Run the client on the Mac where Safari and TabPilot are.

More fixes are on the support page.

Questions

Why does Claude Desktop need Node.js and Claude Code doesn’t?

Claude Code can connect to an MCP server over HTTP itself. Claude Desktop’s config file starts local programs, so it runs the mcp-remote bridge with npx, which needs Node.js.

Can I connect from another computer, a virtual machine or a container?

No. TabPilot’s server listens only on 127.0.0.1, which is reachable from programs running directly on the same Mac and nothing else. That’s deliberate.

Which transport does TabPilot use?

Streamable HTTP, at http://127.0.0.1:47823/mcp, with the token in an Authorization: Bearer header.

Does the TabPilot app have to stay open?

Yes. The app is the server. While it’s closed, no client can connect, and the Safari tools stop working until you open it again.

More guides

TabPilot — MCP for Safari

Let your agent use your real Safari, with per-site access and your approval before anything risky.

Coming soon to the Mac App Store

One-time purchase · macOS 14 Sonoma or later · Try the demo store