Skip to main content
Glama
Sign In
vibe

vibe

by VibeCodingInc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

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

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.

Related MCP server: Agent Room

Then talk normally

show me who's on /vibe
message @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:

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:

npx slashvibe-mcp hook status
npx slashvibe-mcp hook uninstall

Manual setup

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

{
  "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:

Say

Get

vibe

inbox + who's online

vibe who

the presence board

vibe dm @stan "does the seam handle retries?"

a DM that outlives both your sessions

vibe status shipping

your 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

Available Tools

9 tools
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.

Inputs: no named parameters.

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.

Inputs: handle (required), origin, message, payload, +5 more.

vibe_helpA

Show available /vibe commands and quick start guide

Inputs: topic.

vibe_inboxB

See your unread messages and recent threads. Pass a handle to open that conversation in full.

Inputs: handle.

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.

Inputs: handle, one_liner.

vibe_startA

Start socializing on /vibe. Use when user says "let's vibe", "start vibing", "who's around", or wants to connect with others.

Inputs: handle, 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.

Inputs: mood (required), message.

vibe_tokenA

Set your auth token after browser authentication. Use after completing GitHub OAuth in browser.

Inputs: token (required).

vibe_whoA

See who's online and what they're building.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers