Drive your real, logged-in Chrome from any MCP client — even from a remote machine, no inbound port.
registry version 0.3.6
npm
npx -y @vibebrowser/mcpnpm
npx -y @vibebrowser/mcp@0.3.6Streamable HTTP
https://relay.api.vibebrowser.app/mcp/{session_id}
Pick your client — the config below is generated for this server (both local and hosted-endpoint forms). Copy respects the “Pin version” switch above.
claude_desktop_config.json
{
"mcpServers": {
"vibe-mcp-2": {
"command": "npx",
"args": [
"-y",
"@vibebrowser/mcp"
]
}
}
}{
"mcpServers": {
"vibe-mcp-2": {
"command": "npx",
"args": [
"-y",
"@vibebrowser/mcp@0.3.6"
]
}
}
}Remote (hosted) endpoint
https://relay.api.vibebrowser.app/mcp/{session_id}Claude Desktop: Settings → Connectors → Add custom connector, paste this URL.
Format verified against the official Claude Desktop docs ↗.
terminal
claude mcp add vibe-mcp-2 -- npx -y @vibebrowser/mcp
claude mcp add vibe-mcp-2 -- npx -y @vibebrowser/mcp@0.3.6
terminal
claude mcp add --transport http vibe-mcp-2 https://relay.api.vibebrowser.app/mcp/{session_id}Format verified against the official Claude Code docs ↗.
.cursor/mcp.json
{
"mcpServers": {
"vibe-mcp-2": {
"command": "npx",
"args": [
"-y",
"@vibebrowser/mcp"
]
}
}
}{
"mcpServers": {
"vibe-mcp-2": {
"command": "npx",
"args": [
"-y",
"@vibebrowser/mcp@0.3.6"
]
}
}
}.cursor/mcp.json (hosted endpoint)
{
"mcpServers": {
"vibe-mcp-2": {
"url": "https://relay.api.vibebrowser.app/mcp/{session_id}"
}
}
}Format verified against the official Cursor docs ↗.
.vscode/mcp.json
{
"servers": {
"vibe-mcp-2": {
"command": "npx",
"args": [
"-y",
"@vibebrowser/mcp"
]
}
}
}{
"servers": {
"vibe-mcp-2": {
"command": "npx",
"args": [
"-y",
"@vibebrowser/mcp@0.3.6"
]
}
}
}.vscode/mcp.json (hosted endpoint)
{
"servers": {
"vibe-mcp-2": {
"type": "http",
"url": "https://relay.api.vibebrowser.app/mcp/{session_id}"
}
}
}Format verified against the official VS Code docs ↗.
mcp_config.json
{
"mcpServers": {
"vibe-mcp-2": {
"command": "npx",
"args": [
"-y",
"@vibebrowser/mcp"
]
}
}
}{
"mcpServers": {
"vibe-mcp-2": {
"command": "npx",
"args": [
"-y",
"@vibebrowser/mcp@0.3.6"
]
}
}
}mcp_config.json (hosted endpoint)
{
"mcpServers": {
"vibe-mcp-2": {
"serverUrl": "https://relay.api.vibebrowser.app/mcp/{session_id}"
}
}
}Format verified against the official Windsurf docs ↗.
⭐ 3 stars · 最近更新于 28 天前 · Apache-2.0 license
Vibe MCP Browser Automation for AI Agents MCP server for Vibe AI Browser — drive your real, logged in Chrome from any MCP client, including agents running on a different machine with no inbound port open. ⚠️ Security — treat your relay URL/UUID like a password. A relay URL or extension UUID ( wss://…
Summary from the project README — github.com/VibeTechnologies/vibe-mcp
Distributed as npm, Streamable HTTP, listed under Browser Automation. Review our MCP security guide before granting access to real data.
Vibe MCP Browser Automation for AI Agents MCP server for Vibe AI Browser — drive your real, logged in Chrome from any MCP client, including agents running on a different machine with no inbound port open. ⚠️ Security — treat your relay URL/UUID like a password. A relay URL or extension UUID ( wss://
Run the install command shown above, then paste the config for your client (Claude Desktop, Claude Code, Cursor, VS Code or Windsurf) into its MCP settings and restart the client.
The MCP server itself is free to install. The source is public on https://github.com/VibeTechnologies/vibe-mcp. Any third-party service it calls may require its own API key and account.
Any MCP-compatible client can use it, including Claude Desktop, Claude Code, Cursor, VS Code, Windsurf and custom agents.
Publish this server? Link back with a badge on your README or site — copy either snippet.
Markdown
[](https://mcpnav.net/server/vibe-mcp-2/)
HTML
<a href="https://mcpnav.net/server/vibe-mcp-2/"><img src="https://mcpnav.net/badge/vibe-mcp-2.svg" alt="Listed on MCPNav" height="20"></a>