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.
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.
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.
The Vibe relay bridges the connection to the Chrome extension on your machine, so Claude acts in the browser you are already signed into.
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.
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.
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.
The Vibe relay bridges the connection to the Chrome extension on your machine, so Claude acts in the browser you are already signed into.
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.
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.
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.
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
Google Workspace, MCP access for other agents, reusable skills, and a secure secrets vault.
Gmail + Calendar actions built in for real workflows, not brittle APIs.
Expose your browser as an MCP server so other AI agents can drive it.
Securely connect remote agents to your logged-in browser without VPNs.
Create reusable skills and share them across your team or clients.
Internal vault with a password-fill tool that never exposes secrets to the LLM.
Works with Vibe AI, Anthropic Claude Max, GitHub Copilot, and BYOK providers.
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.
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.
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.
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.
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.