Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VIBE_REMOTE_URLNoFull WebSocket URL for connecting to the Vibe extension via an explicit relay endpoint.
VIBE_REMOTE_UUIDNoExtension UUID for connecting to the Vibe extension via the default public relay (wss://relay.api.vibebrowser.app/<uuid>).
VIBE_CHROME_CHANNELNoOverride the Chrome channel (stable, canary, beta, dev) when using --devtools mode.
VIBE_CHROME_USER_DATA_DIRNoOverride 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

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