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. |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/VibeTechnologies/vibe-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server