Give Claude on the web control of your browser

The problem

• Claude Desktop can run a local MCP server; Claude on the web, in a Cowork session, or on your phone cannot — it has no way to spawn a process on your machine.
• So the moment you leave the desktop app, Claude loses access to your browser and to everything behind your logins.
• Web search is not a substitute: it sees the anonymous public internet, not your dashboards, your inbox, or your admin panels.

What Vibe MCP changes

• A custom connector is just a URL, so it works from every Claude surface at once — web, Cowork, desktop, mobile.
• Setup is one paste: no client id, no secret, no consent screen, nothing to configure beyond the URL itself.
• The Vibe relay bridges that connection to the Chrome extension on your machine, so Claude acts in the browser you are already signed into.
• Nothing to install beyond the extension: no npx, no local server, no second browser profile.
• Toggle it per conversation, so a chat only reaches your browser when you want it to.

Set it up in 3 steps

1. 1Install the Vibe extension in Chrome

   Add Vibe AI Browser from the Chrome Web Store (Chrome, Brave, Edge, or any Chromium browser). This is the piece that lets an agent drive the browser you are already logged into — no second browser profile, no re-authentication.

2. 2Add the connector under Settings → Connectors → Add → Add custom connector

   First copy your connector URL: click the Vibe icon → Settings → turn on "Enable external AI agent control" → choose Remote (internet) → copy the Agent connection URL. It is https://relay.api.vibebrowser.app/mcp/ followed by your routing UUID. Then in Claude on the web open Settings → Connectors, click Add, then Add custom connector, give it a name (for example "Vibe Browser") and paste that whole URL. Custom connectors are a paid-plan feature; check your plan if the option is missing. Redact the UUID before sharing any screenshot of this screen.

   Vibe extension → Settings → Agent connection URLurl

   https://relay.api.vibebrowser.app/mcp/<your-routing-uuid>

3. 3Enable it in a chat and make sure your browser is reachable

   In a conversation, use the + button → Connectors and toggle Vibe on for that chat. Claude then discovers the tool list — 27 browser tools at the time of writing. Keep the browser open with the Vibe extension running, "Enable external AI agent control" on, and the mode set to Remote (internet); the connector talks to that browser, so if it is closed there is nothing on the other end.

Your relay URL / extension UUID grants live control of your browser session. Treat it like a password: never commit it or paste it into a shared chat.

What “connected” looks like

• The connector appears in the Settings → Connectors list with its name and a tool count — 27 tools on the current extension build.
• Right after you add it, Claude shows "You are not connected to Vibe Browser yet". This is expected and does not mean the setup failed. Claude only marks a connector as connected once a chat has actually invoked one of its tools — send a prompt first, then re-check.
• In a chat, the + button → Connectors lists Vibe with a toggle. Turn it on for that conversation.
• On the first real request you will see Claude call tools such as New page and Take snapshot, and your own browser will visibly navigate.

Verify it actually works

Do not trust a green checkmark. Run this prompt in a conversation with the connector enabled and check the answer yourself.

Go to duckduckgo.com and find out when the first GPT model was released.

Expected answer: 2018

Pick this over "open google.com" because a wrong answer is unmistakable: the assistant cannot satisfy it from memory-free small talk, and you can watch the tab actually navigate. If the answer comes back as 2018 and you saw your browser move, the connector is wired end to end. If the assistant answers 2018 without your browser doing anything, it answered from its own knowledge — ask it again and require it to cite the page it opened.

Troubleshooting

Tools Claude (web, Cowork & mobile) gets

How it compares

Claude (web, Cowork & mobile) browser control — FAQ

Can Claude control my browser from claude.ai, not just Claude Desktop?

Yes, via a custom connector. Claude Desktop can launch a local MCP server, but claude.ai, Cowork, and mobile cannot — they need a remote MCP server reachable over the public internet. The Vibe relay is exactly that, so one connector URL covers every Claude surface.

How do I add a custom connector in Claude?

Open Settings → Connectors, click Add, then Add custom connector. Give it a name, paste https://relay.api.vibebrowser.app/mcp/ followed by your routing UUID, and click Add. Then in a chat use the + button → Connectors and toggle it on for that conversation.

Claude says "You are not connected to Vibe Browser yet" — did it fail?

No. Claude reports a custom connector as not connected until the first time a conversation actually calls one of its tools. Send a prompt that requires the browser — for example asking it to open a page — and the status resolves. If tool calls then fail, see the troubleshooting table.

Do I need to verify a domain or get allowlisted?

No. Claude needs no domain verification and no allowlist request for a custom connector, and there is no consent screen to approve — you paste the connector URL and that is the whole setup.

Does this work in a Cowork session?

Yes. A custom connector is brokered through your Claude account rather than tied to one machine, so a Cowork session reaches it the same way a Desktop chat does. A local Desktop Extension would not — that is scoped to the desktop app on that one computer.

Do I still need to install anything?

Only the Vibe Chrome extension. On the remote-connector path there is no npx command and no local MCP server — the hosted assistant talks to the Vibe relay over HTTPS, and the relay forwards to your extension.

What exactly do I paste into the connector?

One URL: https://relay.api.vibebrowser.app/mcp/ followed by your routing UUID, which you copy from the Vibe extension → Settings → Agent connection URL. There is no consent screen, no client id, no secret field and no scopes to approve — the URL is the whole configuration.

Why does this use a URL path when the /mcp docs use an X-Remote-Session header?

Because of what the client can send, not because they are different products. A full MCP client (Claude Code, Cursor, VS Code, Codex, OpenCode, Copilot CLI) lets you set request headers, so it can point at https://relay.api.vibebrowser.app/mcp and pass the routing UUID as an X-Remote-Session header — which keeps the credential out of URLs, proxy logs and browser history. A hosted connector UI (Claude on the web, ChatGPT apps) gives you one text field and no header editor, so the only place the UUID can ride is the URL path: https://relay.api.vibebrowser.app/mcp/<your-routing-uuid>. Same relay, same browser, same tools. If your client can send headers, prefer the header form.

I set this up earlier with a consent screen — what do I do now?

Remove the old connector and add it again with the direct URL. In Claude: Settings → Connectors, delete the Vibe entry, then Add → Add custom connector and paste https://relay.api.vibebrowser.app/mcp/ followed by your routing UUID. In ChatGPT: Settings → Security and login → Developer mode → Plugins, delete the old app, then Create app with the same URL. Editing the URL in place is unreliable because clients cache what they discovered the first time. Once re-added, no approval step appears — the connector just starts listing tools.

Is the UUID in the connector URL a secret?

Yes. That UUID is the credential that routes an agent to your browser — anyone who has it can drive your logged-in session. Treat the URL like a password: never post it in a shared chat, screenshot, README, or issue. If it leaks, regenerate it in the Vibe extension settings and the old UUID stops routing immediately.

How do I revoke access?

Two ways, either is enough. Remove the Vibe connector inside the assistant. Or open the Vibe extension → Settings and turn "Enable external AI agent control" off, which cuts every client off from this browser at once. To invalidate the URL itself, regenerate the connection URL in the extension.

What can an assistant do once it is connected?

Everything the extension exposes: list and switch tabs, read page text and HTML, take screenshots and accessibility snapshots, navigate, click, type and fill forms, scroll, use keyboard shortcuts, and open or close tabs — inside the sessions you are already logged into. Connect it only to an assistant you trust with those sessions.

What is the difference between this and the local MCP server?

The local path (npx @vibebrowser/mcp) runs on your machine and suits desktop clients that can spawn a process — Claude Desktop, Cursor, VS Code, Codex CLI. The remote path suits hosted assistants that only accept a URL. Both end up driving the same Chrome tab through the same extension.

Does my page content go through your servers on this path?

Yes — unlike the local STDIO path, tool calls and their results traverse the Vibe relay, because the assistant is running in the vendor cloud and cannot reach your machine directly. If you need page content to never leave your machine, use the local MCP server with a desktop client instead.

Works with your other agents too

The same MCP server powers every client. Multiple agents can drive the same browser at once.