Vibe MCP — Real Chrome, Remotely

Drive your real, logged-in Chrome from any MCP client — even from a remote machine, no inbound port.

What does this entry provide?

Vibe MCP — Real Chrome, Remotely is an MCP server entry in ChatHome Skills, sourced from Official MCP Registry and scored 73/100. As a Model Context Protocol server, it exposes tools that MCP-compatible LLM clients such as Claude, Cursor, and Copilot can call directly, extending an agent's reach beyond its built-in capabilities. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding Vibe MCP — Real Chrome, Remotely to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.

Snapshot facts

Source: Official MCP Registry
Quality: 73/100
Install method: streamable-http
Repo: VibeTechnologies/vibe-mcp
Repo updated: Aug 21, 2026

Install command

mcp add io.github.VibeTechnologies/vibe-mcp https://relay.api.vibebrowser.app/mcp/{session_id}

Install method: streamable-http

Review the upstream source before running this command.

GitHub project Homepage

Quality

Repo stars

Repo updated

Aug 21, 2026

How is this score calculated?

Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.

MCP manifest

{
  "_meta": {
    "io.modelcontextprotocol.registry/official": {
      "status": "active",
      "isLatest": true,
      "updatedAt": "2026-08-21T09:43:18.495552Z",
      "publishedAt": "2026-08-21T09:43:18.495552Z",
      "statusChangedAt": "2026-08-21T09:43:18.495552Z"
    }
  },
  "server": {
    "name": "io.github.VibeTechnologies/vibe-mcp",
    "title": "Vibe MCP — Real Chrome, Remotely",
    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
    "remotes": [
      {
        "url": "https://relay.api.vibebrowser.app/mcp/{session_id}",
        "type": "streamable-http",
        "variables": {
          "session_id": {
            "isSecret": true,
            "isRequired": true,
            "description": "Your personal agent-connection ID from the Vibe extension (Vibe icon -> Settings -> AI Agent Control -> Remote (internet) -> Relay access). Paste the URL as-is: this endpoint is plain Streamable HTTP with no OAuth, no dynamic client registration and no scope setup. Migration: the retired consent-screen connector at a bare /mcp is unsupported -- remove it and re-add this direct URL. The ID is a bearer capability granting full control of that browser: never share it, and regenerate the session in the extension to revoke it."
          }
        }
      }
    ],
    "version": "0.3.6",
    "packages": [
      {
        "version": "0.3.6",
        "transport": {
          "type": "stdio"
        },
        "identifier": "@vibebrowser/mcp",
        "registryType": "npm",
        "registryBaseUrl": "https://registry.npmjs.org"
      }
    ],
    "repository": {
      "url": "https://github.com/VibeTechnologies/vibe-mcp",
      "source": "github"
    },
    "websiteUrl": "https://vibebrowser.app",
    "description": "Drive your real, logged-in Chrome from any MCP client — even from a remote machine, no inbound port."
  }
}

Report an issue with this listing