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:
- 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. - 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."
- 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.
- Copy the address and add it to your AI app as below (there is no code to type).
- 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.
- 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.
- 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.
- 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).
- Open https://chatgpt.com/plugins and add an MCP server with the address.
- 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
- ChatGPT for Mac: Settings → Plugins → MCPs → Add. Choose the type Streamable HTTP (the switch is easy to miss), paste the address, save, then Authenticate.
- Codex:
codex mcp add <name> --url <address>, thencodex mcp login <name>(the desktop app shows Authenticate).
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
- "Open “Connect your AI app” first" or "Open the page first" during the sign-in: the page's dialog is closed, or its tab is closed or asleep. Open the page, click "Connect your AI app", then Try again. With tab-mcp for Chrome, open its side panel and click "Turn on AI access", or "+ Add another AI app" once an app is paired.
- The AI app says the page is not open: its tab is closed, asleep or disconnected. Open it; the address stays the same. On a phone or tablet, the browser pauses pages that are not on screen, so while you are in the AI app it cannot reach the page. On Android, put the browser and the AI app side by side in split screen. On an iPad, Split View may work (not tested); an iPhone has no split screen.
- The AI app waits on a tool and nothing happens: the page asks you before some tools run, in its own tab, which is often in the background while you are in the AI app. Its tab title then starts with "Allow?". Switch to that tab and answer. Without an answer, the call ends after at most about 5 minutes ("The page did not answer in time."; some AI apps stop waiting sooner). With tab-mcp for Chrome, the question is in its side panel or a Chrome notification instead, and without an answer it is refused after 1 minute ("The user was asked and did not answer within 60 s.").
- The AI app says "The user declined": "Don't allow" was chosen in the page's question, it was closed with Escape, or the AI app gave up on the call while the page asked. Ask the AI app to try again and choose Allow. (With tab-mcp for Chrome: "The user did not allow this call.")
- "Another tab or program took over this page": the page's address is in use elsewhere. If you opened the page in another browser (or, rarely, another tab), close this notice and use that one. If not, someone may have a copy of the address: click "New address". It disconnects every AI app from the old address; then add the new address to your AI apps again, as above. "Opened in another tab" is the harmless case: your AI apps now use that tab; to use this one again, connect it again.
- The page's dialog says "Could not connect", "The connection was lost." or "The session ended.": check your internet connection, then click "Connect again". While it says "Connection lost. Reconnecting…", the page tries by itself; "Connect again" tries at once.
- "That code has expired": take the current code from the page.
- Signed in, but no tools appear (Codex, ChatGPT for Mac): the feature above is off.
- "This connection cannot be made": the app's sign-in is not supported; the page says why. Check compatibility.