VibeBrowser Co-Pilot for Cowork

AI for Document Research

Claude supports custom connectors backed by a remote MCP server. Open Settings → Connectors → Add → Add custom connector and paste your Vibe connector URL, https://relay.api.vibebrowser.app/mcp/ followed by the routing UUID from the extension. Claude can then navigate, click, type, scroll, screenshot, and read your real Chrome — including pages behind a login. Because the connector is brokered by your Claude account, it works in Cowork and on mobile, not just Claude Desktop.

Why Cowork Choose Vibe

One URL, no local install

Claude Desktop can run a local MCP server; Claude on the web, in a Cowork session, or on your phone cannot. A custom connector is just a URL — no npx, no local server, no second browser profile.

Built for Cowork sessions

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.

Your real Chrome

The Vibe relay bridges the connection to the Chrome extension on your machine, so Claude acts in the browser you are already signed into.

Logged-in pages included

Web search sees the anonymous public internet, not your dashboards, your inbox, or your admin panels. Through Vibe, a Cowork session reads and acts on those pages directly.

Key Capabilities

One URL, no local install

Claude Desktop can run a local MCP server; Claude on the web, in a Cowork session, or on your phone cannot. A custom connector is just a URL — no npx, no local server, no second browser profile.

Built for Cowork sessions

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.

Your real Chrome

The Vibe relay bridges the connection to the Chrome extension on your machine, so Claude acts in the browser you are already signed into.

Logged-in pages included

Web search sees the anonymous public internet, not your dashboards, your inbox, or your admin panels. Through Vibe, a Cowork session reads and acts on those pages directly.

Toggle per conversation

In a chat, tap + → Connectors and turn Vibe on. Toggle it per conversation, so a chat only reaches your browser when you want it to.

Nothing beyond the URL to configure

No client id, no secret, no consent screen, and no domain verification or allowlist request — you paste the connector URL and that is the whole setup. Custom connectors need a paid Claude plan.

Common Workflows

Ask a Cowork session to research across pages in your logged-in browser

Have Cowork read a dashboard and draft a summary from the real numbers

Let Cowork gather information from several sites into one document

Ask Cowork to check your inbox page for a specific message

Have Cowork fill a web form from a brief you give it

Integrations & Agent Ecosystem

Google Workspace, MCP access for other agents, reusable skills, and a secure secrets vault.

Google Workspace Native

Gmail + Calendar actions built in for real workflows, not brittle APIs.

MCP Server for Agents

Expose your browser as an MCP server so other AI agents can drive it.

Remote Browser Relay

Securely connect remote agents to your logged-in browser without VPNs.

Skills Library

Create reusable skills and share them across your team or clients.

Secrets Vault + Type-In

Internal vault with a password-fill tool that never exposes secrets to the LLM.

Model & Agent Choice

Works with Vibe AI, Anthropic Claude Max, GitHub Copilot, and BYOK providers.

Works With Your Tools

Claude
Cowork
Chrome
Gmail
Google Drive
Notion
Slack
GitHub

Frequently Asked Questions

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.

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.

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.

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.

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.