Developer · Remote MCP server
Vibe MCP - Real Chrome, Remotely
Drive your real, logged-in Chrome from any MCP client - even from a remote machine, no inbound port.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.VibeTechnologies/vibe-mcp- Version
- 0.3.6
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-21
- Updated
- 2026-08-21
- Publisher
- VibeTechnologies (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/VibeTechnologies) · how
- Website
- vibebrowser.app
- Repository
- github.com/VibeTechnologies/vibe-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://relay.api.vibebrowser.app/mcp/{session_id} | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @vibebrowser/mcp | 0.3.6 | stdio |
How to connect 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
More developer servers
| Server | Runs |
|---|---|
| Vibe Coding 中文助手Read-only Chinese Vibe Coding knowledge connector for search, docs, and repo freshness. | Remote · HTTPLive check: ✓ handshake |
| Vibe DoctorCheck a deployed web app for security headers, SEO, accessibility and performance, with a grade. | Remote · HTTPLive check: ✓ handshake |
| Vibe HnindexIndex source code into a local knowledge base, search with keyword + semantic + hybrid modes. | Local · stdio |
| Vibe MCPSocial layer for Claude Code - DMs, presence, discovery, and games between AI-assisted developers. | Local · stdio |
| Vibecheck MCPAI Code Firewall - MCP Server for hallucination prevention in AI development. | Local · stdio |
| VibedeployDeploy and host AI-built websites on EU infrastructure, straight from your AI agent. | Remote · HTTPLive check: ✓ handshake |
| VibeFixTests your live published app like a first customer, whatever built it. Free test; fixes on a plan. | Remote · HTTPLive check: ✓ handshake |
| VibeHackerProduct Hunt for AI tools. Search, submit, upvote from Claude Code or Cursor. | Remote · HTTPLive check: ✓ handshake |