Skip to content

Connecting an AI app

How to add a page's tab-mcp address to an AI app. Agents in the browser that call the page's tools through WebMCP need none of this. AI apps change their menus often: if a step no longer matches, look for "connector", "MCP server" or "plugin" in the app's settings. Which apps work at all: compatibility.

Every app needs the same two things from the page:

  1. In the page, click "Connect your AI app" and copy the address (https://…/a/…/mcp). Keep the page and the dialog open until the app shows it is connected: the code works only while the dialog is open.
  2. When the app asks you to sign in, your browser opens the relay's page "Connect … from …". Type the 6-digit code the page shows (it changes every 2 minutes) and click Connect.

With tab-mcp for Chrome, the address and the code are in the extension's side panel instead: "Turn on AI access", or "+ Add another AI app" once an app is paired.

Keep the defaults for sign-in wherever an app asks (OAuth, no client ID or secret).

Pages where you sign in instead of typing a code

Some pages connect AI apps through your account on the page instead of a code. Their dialog shows no code and says "When your AI app asks, sign in with the account you use on this page. No code is needed."

  1. Sign in to the page first. Until the page knows who you are, its dialog shows no address and says "Sign in to this page first." or "Checking your sign-in…". If it says "Your sign-in on this page was not accepted", sign out of the page and in again.
  2. Copy the address and add it to your AI app as below (there is no code to type).
  3. When the app asks you to sign in, your browser opens the relay's page "Connect … from …". Click Connect, then sign in with the same account as on the page.

The connection belongs to that account: when you sign out of the page, the page's AI connections end. If you sign in with another account, the sign-in page says "This AI tool is logged in as someone other than the page.": click Connect again and choose the account you use on the page.

Claude (claude.ai and Claude Desktop)

As of claude.ai on 2026-10-25 and Claude for Mac 3.6556.2.

  1. Settings → Connectors → Add custom connector. Enter a name and the address, then Add. Claude detects "Sign in now" and "Use Claude's published identity" by itself.
  2. Click Connect. Claude Desktop opens your browser and claude.ai asks to finish connecting; continue. Type the code, and the browser hands you back to the app.
  3. In a new chat, turn the connector on in the tools menu.

The relay's page names the app "Claude from claude.ai" in both cases: the desktop app signs in as claude.ai.

ChatGPT on the web

As of chatgpt.com on 2026-10-25 (relay 0.5.1 or later).

  1. Open https://chatgpt.com/plugins and add an MCP server with the address.
  2. Connect, then type the code on the relay's page.

ChatGPT for Mac and Codex

As of ChatGPT for Mac 26.1016 and Codex 0.163. The Mac app's MCP servers are Codex's (~/.codex/config.toml), so the two need the same feature turned on first:

codex features enable mcp_2026_07_28

Codex loads tools when a chat starts: start a new chat after connecting. Each page has its own address, so each needs its own entry.

The feature applies to all of Codex's MCP servers, and so to the Mac app's. If another server stops working with it, turn it off again (tab-mcp's entries then show no tools):

codex features disable mcp_2026_07_28

Claude Code

As of Claude Code 2.1.308 on 2026-10-26.

claude mcp add --transport http <name> <address>

Then run /mcp in Claude Code and choose Authenticate.

When it does not work