Vibe MCP — Real Chrome, Remotely

Vibe MCP — Real Chrome, Remotely is a remote MCP server: there is nothing to install. Its endpoint is https://relay.api.vibebrowser.app/mcp/{session_id}, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The URL contains placeholders to fill in before connecting: {session_id}.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Node.js package published to the npm registry: @vibebrowser/mcp version 0.3.6. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @vibebrowser/mcp@0.3.6.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "vibe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@vibebrowser/mcp@0.3.6"
      ]
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect