Vibe MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIBE_REMOTE_URL | No | Full WebSocket URL for connecting to the Vibe extension via an explicit relay endpoint. | |
| VIBE_REMOTE_UUID | No | Extension UUID for connecting to the Vibe extension via the default public relay (wss://relay.api.vibebrowser.app/<uuid>). | |
| VIBE_CHROME_CHANNEL | No | Override the Chrome channel (stable, canary, beta, dev) when using --devtools mode. | |
| VIBE_CHROME_USER_DATA_DIR | No | Override the Chrome user data directory when using --devtools mode. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| set_remoteA | Set the remote relay target for this MCP server. If browser tools are missing, call set_remote first to connect to a Vibe relay. The routing UUID in the URL is the sole bearer credential for the relay session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly stated.
The single tool name 'set_remote' follows a clear verb_noun convention, which is consistent and predictable. With only one tool, naming consistency is perfect.
A single tool feels insufficient for a server named 'Vibe MCP', especially since the description references browser tools that are missing. The tool is purely a configuration step, leaving the server with very limited functionality.
The tool set lacks any browser automation tools, which are the implied core functionality of the server. The description suggests that set_remote is a prerequisite for browser tools, but those tools are not present, creating a noticeable gap. The server cannot perform any useful task beyond configuration.