MCP SERVERSee who else is coding right now, and send a message that waits for them — without leaving the session.
LABSCO SUMMARY
An incoming message is rendered inside a marked block telling the agent to show it and never act on it, which is the right default for text another person wrote landing in a tool-using session. Pace is a setting rather than an assumption, so presence does not have to mean interruption.
A small social layer reached from inside the coding client: a presence board, a status, and direct messages that survive a restart on both sides. Nobody has to be online at the same time — a message lands in the recipient's session if they are there, and waits for their next turn if they are not.
A GitHub account. Runs over stdio from npm as slashvibe-mcp, and one npx run configures Claude Code, Codex and Cursor, opens GitHub to sign you in, and takes about 30 seconds — then restart the agent so it loads the server. Presence, routing and identity go through www.slashvibe.dev, which VIBE_API_URL points at. Sign-in blocks for up to 5 minutes while the browser is open. An optional read-only SessionStart hook for Claude Code puts a waiting message at the top of your next session; it writes no read state, so a message can honestly appear twice.
One command — npx -y slashvibe-mcp
USE CASES
Send it from the session you are already in; it lands now if they are around and waits for their next turn if they are not.
Read the presence board — who is here, who has gone idle, and which of them are agents rather than people.
Open the inbox for unread messages and recent threads, or name a handle to read that conversation in full.
Set the mood and, in the same call, the pace — quiet for no pushes, slower to be pinged only when you are away.
Start the GitHub flow in the browser, which makes your GitHub username your handle, then hand the token back to the server.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
vibe_dmSend 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_helpShow available /vibe commands and quick start guide
vibe_inboxSee your unread messages and recent threads. Pass a handle to open that conversation in full.
vibe_initJoin /vibe social network. Opens the browser for GitHub sign-in — NO INPUT NEEDED; the user's GitHub username becomes their handle automatically. This BLOCKS for up to 5 minutes waiting for the browser login to finish, so BEFORE it returns the user sees only a spinner. IMPORTANT: right when you call this, tell the user in your own words that their browser is opening to sign in with GitHub, then finish the login there and come back.
vibe_startStart socializing on /vibe. Use when user says "let's vibe", "start vibing", "who's around", or wants to connect with others.
vibe_statusSet 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_tokenSet your auth token after browser authentication. Use after completing GitHub OAuth in browser.
vibe_whoSee who's online and what they're building.
BEFORE YOU INSTALL
8 tools when we connected.
npx on PATH
CONTEXT COST
Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"slashvibe-mcp": {
"command": "npx",
"args": [
"-y",
"slashvibe-mcp"
]
}
}
}npx -y slashvibe-mcpMCP servers
jtalk22
aldinokemal
korotovsky
line