One command, with your token in it.
Create a token on the dashboard's Tokens page and
put it where tt_live_… is:
claude mcp add --transport http browser \
https://tabtunnel.dev/v1/mcp \
--header "Authorization: Bearer tt_live_…"
browser is the name Claude Code will show for it; call it what you
like. Adding --scope project saves it in the current repository's
.mcp.json instead of your own settings — but that file then contains
your token, so do not commit it.
claude mcp list
Then, in a session, ask it to list your browsers. Yours should come back with the name you gave it during setup. If it has not been used for a while, the first command takes a few seconds.
401 Unauthorized |
The token no longer works. Create a new one on Tokens and put it in place of the old one. |
| No browsers listed | The token is for a different organization from your browser. Check which organization is shown at the top of the dashboard, then create the token there. |
Your browser is offline |
Open Chrome and check the TabTunnel extension is signed in. connected and reachable both mean it is ready. |
| Chrome asks about a site | Answer it and the agent carries on. This happens the first time an agent visits a site, unless you chose Allow everything during setup. |
Next: what it can do.
Is something here wrong, or missing? Tell us.