vibe
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| resources | {} |
| extensions | {
"io.modelcontextprotocol/ui": {
"mimeTypes": [
"text/html;profile=mcp-app"
]
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vibe_startA | Start socializing on /vibe. Use when user says "let's vibe", "start vibing", "who's around", or wants to connect with others. |
| vibe_initA | Sign in to /vibe with GitHub — NO INPUT NEEDED; the GitHub username becomes the handle. Returns IMMEDIATELY with an auth_required state, the login URL, and one sentence to relay: 'Open this, sign in with GitHub, then say vibe start.' It may open a browser when one is available locally (never over SSH/headless); it never waits. Sign-in completes in the background; the next vibe start recognizes it. |
| vibe_tokenA | Set your auth token after browser authentication. Use after completing GitHub OAuth in browser. |
| vibe_whoA | See who's online and what they're building. |
| vibe_statusA | Set your mood/status, or your notification pace. Mood: shipping, thinking, afk, debugging, pairing, deep, celebrating, struggling, away, back, clear. Pace: slower (only ping when away), quiet (no pushes), normal. |
| vibe_dmA | Send a direct message to someone on /vibe. It lands in their session now if they're around, or waits for their next turn — nobody has to be online. Sends exactly the text you give it; /vibe doesn't attach repository or session context. |
| vibe_inboxB | See your unread messages and recent threads. Pass a handle to open that conversation in full. |
| vibe_helpA | Show available /vibe commands and quick start guide |
| vibe_capabilitiesA | Report the local capability manifest for this runtime: remember, reflect, message, call — each as granted, available, off, or unavailable, with the honest reason. Read-only; reads no private data; installs nothing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| presence_board | Live presence board — who's online on /vibe and what they're building |
TDQS
Scored across 9 tools
Most tools have distinct responsibilities: status, inbox, dm, who, init, and token are all clearly separated. The only mild ambiguity is between vibe_init and vibe_token (both auth-related) and vibe_help vs vibe_capabilities (both informational), but their descriptions make the different purposes clear enough.
All tools share the consistent vibe_ prefix and lowercase snake_case, but the suffixes mix nouns (status, inbox, token), verbs (start, init), and a question word (who). The prefix makes names predictable, but the second part does not follow a consistent verb_noun pattern.
Nine tools is a well-scoped count for a social presence and messaging server. Each tool covers a distinct part of the workflow without feeling redundant or bloated.
The tool set covers the core social workflow: authenticate, start, set status, see who's online, send DMs, and read the inbox. Some nice-to-have operations like an explicit logout or richer thread management are missing, but the main user journey is fully supported.