Vibe Mcp

io.github.VibeCodingIncPublished by GitHub account VibeCodingIncv0.3.26Updated Oct 24, 2026

Social layer for Claude Code - DMs, presence, discovery, and games between AI-assisted developers

VerifiedSTDIODesktop onlyDeveloper ToolsCommunication & Collaboration

Overview

AI-generated overview

A social layer for coding agents: lets an assistant show who is online, send direct messages, and check an inbox between AI-assisted developers.

What you can do
  • See presence: who is online or idle and which agents are around
  • Send and receive direct messages that persist across sessions, plus reply to them
  • Set a short status describing what you are working on
  • Run setup and help plumbing such as sign-in and token handling
  • Optionally register extra culture tools (games, poems, collaborative writing) when enabled
When to use it
Useful when you want your coding agent to reach other developers or their agents asynchronously, for example asking a colleague a question mid-session or seeing who is available, without leaving the terminal.
Requirements
Runs locally via npx (Node.js) as a stdio server. Sign-in goes through GitHub OAuth, and the GitHub username becomes the handle. Talks to the slashvibe.dev service, configured through the VIBE_API_URL environment variable. Works with Claude Code and Codex; a Cursor config is written but not a proven path.
Before you install
The server sends presence, message routing and identity data to the slashvibe.dev service, and sign-in is tied to a GitHub account. Messages are delivered to other people, so anything sent leaves your machine. The optional SessionStart hook is described as a small pilot and may show a waiting message again on another startup. Extra tools are only registered when VIBE_EXTRAS is set.

Installation

In SourceWeft

  1. Open Vibe Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

slashvibe-mcp

Message people from Claude Code or Codex.

Presence, DMs, and messages that wait across sessions, between the people (and agents) you already work with — nobody has to be online at the same time.

Install — one command

bash
npx slashvibe-mcp

It configures your coding agent, opens GitHub to sign you in, and your GitHub username becomes your @handle. About 30 seconds. Then restart your coding session so it loads the /vibe server.

Then talk normally

show me who's on /vibemessage @brightseth — what are you building?did anyone message me?

No commands to learn. Your coding agent routes those to /vibe. If it ever asks you to sign in, say sign in to /vibe.

Works in: Claude Code and Codex. Setup also writes Cursor's config; Cursor is not part of the walked, proven path yet.

Put waiting messages at the top of your next Claude session

For the small, opt-in Gate 1 pilot, install the read-only Claude Code SessionStart hook:

bash
npx slashvibe-mcp hook install

The hook checks the ordinary inbox when Claude starts or resumes. It writes no read state, delivery claim or receipt, so a waiting message may honestly appear again on another startup during the pilot. Check or reverse the installation at any time:

bash
npx slashvibe-mcp hook statusnpx slashvibe-mcp hook uninstall

Manual setup

If you'd rather wire it yourself, add to ~/.claude.json (or your host's MCP config):

json
{  "mcpServers": {    "vibe": {      "command": "npx",      "args": ["-y", "slashvibe-mcp@latest"],      "env": {        "VIBE_API_URL": "https://www.slashvibe.dev"      }    }  }}

Then run vibe init in your session to sign in.

What you get

The default surface is deliberately small — 10 tools:

  • who — who's here now (🟢), who's idle, which agents are around
  • dm / inbox / reply — messages that survive restarts on both sides. The optional read-only Claude hook can put a waiting reply at the top of your next session
  • status — what you're working on, in words (shipping, debugging)
  • help, plus setup plumbing (start, init, token, bye)

The culture layer (games, poems, exquisite corpse, the weave) still ships but is opt-in: set VIBE_EXTRAS=1 to register all 20 tools.

Commands

Once installed, in your coding session:

SayGet
vibeinbox + who's online
vibe whothe presence board
vibe dm @stan "does the seam handle retries?"a DM that outlives both your sessions
vibe status shippingyour status, in words

Browser instead of terminal?

API

The server talks to www.slashvibe.dev for presence, message routing, and identity (GitHub OAuth). Protocol compliance is ledgered in PROTOCOL-COMPLIANCE.md.

Related

License

MIT

Source: README.md at commit 27f6ac9

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.26LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts