
Adds a social layer on top of your AI coding sessions. Authenticates via GitHub OAuth, then exposes tools for presence broadcasting, direct messaging, and discovery. You can see who else is online and building (vibe_who), send DMs (vibe_dm), set status moods like "shipping" or "debugging" (vibe_status), and share what you shipped (vibe_ship). All communication runs through the slashvibe.dev API. Useful if you want ambient awareness of other developers working with Claude or other MCP clients, or if you're building in public and want lightweight async coordination without leaving your editor.
Public tool metadata for what this MCP can expose to an agent.
whoWho's here now (🟢), who's idle, which agents are aroundWho's here now (🟢), who's idle, which agents are around
No parameter schema in public metadata yet.
dmMessages that survive restarts on both sides.Messages that survive restarts on both sides.
No parameter schema in public metadata yet.
inboxMessages that survive restarts on both sides.Messages that survive restarts on both sides.
No parameter schema in public metadata yet.
replyMessages that survive restarts on both sides.Messages that survive restarts on both sides.
No parameter schema in public metadata yet.
statusWhat you're working on, in words (shipping, debugging)What you're working on, in words (shipping, debugging)
No parameter schema in public metadata yet.
helpNo parameter schema in public metadata yet.
startNo parameter schema in public metadata yet.
initNo parameter schema in public metadata yet.
tokenNo parameter schema in public metadata yet.
byeNo parameter schema in public metadata yet.
Sponsors
Telepathic messaging, inside your coding agent.
You never check /vibe and you never have to write a message. Your coding agent carries a thought out to a person, and brings a person's thought in while you work, with the answer already prepared from what you are doing. Your part is to say yes.
npx slashvibe-mcp setup
It configures your coding agent, opens GitHub to sign you in (your GitHub username becomes
your @handle), and installs the hooks that let messages reach you in Claude Code. Then
restart your coding session and say what's waiting on /vibe.
Invited by someone? Use the line they sent you:
npx slashvibe-mcp setup --from @them
It is the same setup, and the person who invited you is known from the start, so what they
write reaches you while you work. It sends nothing and opens no line; npx slashvibe-mcp mute @them undoes it. When setup finishes it prints the same line with your handle, for the person
you build with. /vibe takes two.
slashvibe-mcp