TabTunnel browser automation over MCP Sign in Create account
Free for personal use Chrome extension · your own session

Let your AI assistant work in your own browser.

TabTunnel connects Chrome to Claude Code, Cursor and other AI tools, so they can open tabs, read pages, click, type and take screenshots — in the browser you are already signed into. Everything behind a login simply works.

Start free — personal use Create a business account Install the extension See the request path
one command, any MCP client 
# Claude Code, Cursor, Codex, Cline — anything that speaks MCP
claude mcp add --transport http browser \
  https://tabtunnel.dev/v1/mcp \
  --header "Authorization: Bearer …"
Your logins, your two-factor, your extensions Nothing to run on your machine but Chrome Free forever for personal use
The browsers it can reach example
Work laptop yours · signed into the sites you use connected
Maria’s browser shared with you · she can take it back idle
The test machine your team’s · nobody is signed into it offline

Nothing is picked for you — once there is more than one, your assistant has to ask which. Working inside a colleague’s browser by accident is the mistake this design exists to prevent.

What it does

You ask in plain language. It works in a real tab.

The sites your AI usually can’t reach are the ones you’re logged into. Those are exactly the ones this opens up.

“Check how the new pricing page looks on staging.”

It opens your staging site — already logged in — screenshots the page and tells you what looks off.

“This form keeps failing. What’s going wrong?”

It repeats your steps in the browser and reads the errors the page throws while it does.

“Pull last month’s numbers out of the billing dashboard.”

It navigates the dashboard you’re signed into and reads the figures back. No API, no export.

Where the browser sits decides what it can reach: four things people set it up for.

Setting it up

Three steps, about two minutes

Claude Code, Cursor, Codex, Cline and Zed all speak MCP — the standard way AI tools connect to other software. TabTunnel is MCP for your browser, so if your tool supports MCP, it works.

1

Add the Chrome extension

Sign in once inside Chrome and give the machine a name — “Work laptop”. Nothing else gets installed on your computer.

2

Paste one line into your AI tool

The command at the top of this page is the whole configuration, and the same line covers every machine you add later.

3

Tell it which browser

Your AI lists the browsers it can reach and you pick one. When there’s more than one it always asks — it never guesses.

The request path

One HTTPS call in. One real click out.

Your assistant never talks to your machine directly. It asks TabTunnel for the browser you named, TabTunnel checks you are allowed to use it, and the answer comes back the same way.

How a request reaches your browser Your AI tools on the left send one HTTPS request to TabTunnel, which checks who is asking, checks they are allowed to use that browser, finds the machine and passes the command on to the Chrome extension. The extension does it in a real tab and the answer comes straight back. On the right are the three kinds of browser: your own laptop, a colleague's browser shared with you, and a test machine owned by your team. Every request is written to an audit trail. YOUR AI TOOLS TABTUNNEL · THE HOSTED SERVICE YOUR BROWSERS Claude Code mcp: browser Cursor · Codex · Cline any MCP client Your own scripts over HTTPS one request your token TabTunnel over HTTPS 1 · Check who is asking A token belongs to one person, or to one team 2 · Check they may use that browser Nobody reaches a browser unless it was handed to them — running the team is not a way in. 3 · Find the machine Finds the browser you named, and wakes it if it has gone quiet. 4 · Send it, and send the answer back The page text or the screenshot passes straight through; what is kept is the record of the call. to that one and back Your laptop The extension drives a tab in your own session the sites you are already signed into CONNECTED you chose: ask first A colleague’s browser Shared with you by name, taken back in one click and it ends when they leave the team BUSINESS A test machine Owned by the team, with nobody signed into it set up with a one-time code BUSINESS Who did what the person · the browser · the page · when · allowed or blocked BUSINESS
On your machine

Nothing to run, nothing to open

No proxy, no daemon, no port left listening. Chrome reaches out to us; nothing on the internet reaches in to it.

Speed

Quick once it is awake

A browser you are already working in answers straight away. One that has gone quiet takes a moment to wake, and is quick from then on.

Two at once

Several assistants, one Chrome

Each one keeps to the tabs it opened, so two can work side by side without closing each other’s windows.

The tools

The tools your assistant gets

Element references instead of brittle selectors, page reads as markdown or the accessibility tree, and the console and network panels the browser already has.

Navigate
list_tabs · create_tab
close_tab · activate_tab
navigate · reload
go_back · go_forward · wait_for
Read
read_page · find
screenshot
get_page_info
read_console · read_network
Act
click · type · press_key
hover · scroll
select_option
set_viewport · set_zoom
evaluate_js (on for your own browsers; in a team, off until somebody turns it on)
Plans

Free for you. Paid when a team depends on it.

Everything you need on your own machines is free, and stays free — not a trial, not a tab quota. You pay the day a browser stops being just yours.

Personal
Free forever, for personal use
  • ✓Every browser you own. Laptop, desktop, work machine — no cap.
  • ✓Everything it can do. Read, click, type, screenshot, console, network. Nothing held back.
  • ✓As many assistants as you like, on the same Chrome at once.
  • ✓You decide what it may do without asking first, and what is off limits entirely.
  • ✓Run JavaScript in the page. Yours to use, because the only person who can drive your browser is you.
Create a free account
Business
€1.99 per member, per month
Plus €0.99 per browser, €1.49 per shared browser and €0.99 per browser you open over CDP, a month. You pick how many of each, change it whenever, and pay for nothing you have not asked for.
  • ✓Everything in Personal, for everyone on the team.
  • ✓Share a browser. Lend one of your machines to a named colleague — or to the whole team — and take it back instantly.
  • ✓Test machines. Set up a QA box or a lab machine with a one-time code, owned by the team and signed into by nobody.
  • ✓Playwright and other test frameworks. Switch the Chrome DevTools Protocol on for a browser and drive it from Playwright’s connectOverCDP, Puppeteer, or anything else that speaks CDP — how to connect.
  • ✓A record of what happened — the person, the browser, the page, and whether it was allowed.
  • ✓Team settings. Cap how far consent can go, decide whether evaluate_js may run, set how long tokens live.
  • ✓Single sign-on, invitations, and roles for billing and policy.
Create a business account Talk to us

Line by line, what each plan includes: see the full comparison.

For teams

Three things that only matter with other people

All of them follow one rule: nobody reaches your browser unless you handed it to them. Being the boss is not a way in.

Sharing
Work laptop yours one colleague the whole team

Grant a browser, not a role

Owning or running the team puts nobody inside your Chrome. A colleague reaches a machine only because you handed it to them by name, and their access ends the moment you take it back — or the moment they leave.

Test machines
one-time code test machine nobody signs in

Machines nobody has to log into

A QA box, a staging laptop, a lab machine: set it up with a one-time code instead of signing a personal account into a shared computer. It belongs to the team, holds nobody’s logins, and only the people you name can use it.

The record
maria · clicked · billing.acme.com test machine · screenshot · staging dave · blocked · not allowed there

Every call, with a name on it

The record is written by the service, not by the assistant being watched, and it outlives the browser, the token and the person it names. What was turned down is in it too — a prompt somebody declined is exactly the entry you will want later.

What it will not do

The limits are the product

Handing an assistant a browser that is already logged into everything is only reasonable if the boundaries are real ones.

blocked chrome:// pages, the Web Store, and TabTunnel’s own dashboard — in every mode, so an assistant can never read out its own access.
your call Ask before every new site, allow only your own test sites, or allow everything. Your blocked list always wins, and a team can narrow this but never widen it.
reversible Turn a browser off and anything using it stops at its next action. Removing the extension ends it too, and so does a colleague taking their machine back.
not stored Page text passes through and is gone. What is kept is the record of what was done, not what was on screen.

Give your assistant a browser it can actually use.

Install the extension, paste one line. Free for personal use, no card.

Create account See how it works