Vibe MCP

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

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.

Introduce this user to a real human online who's building something related, so they land mid-conversation instead of staring at an empty inbox. Call this right after vibe_init succeeds (and any time a returning user hasn't connected yet). Pass `building`: a short, specific, first-person-free summary of what the user is actually working on in THIS session — infer it from the current files, project, and recent work (e.g. "an OAuth PKCE login flow in a Next.js app", "a Postgres migration for a chat schema", "a Tauri menubar app"). The tool finds the best-matched online human and drafts a warm tw…

Put YOURSELF on the /vibe people list so others can find you and message you, with a short line about what you are building. Opt-in and reversible (vibe_unlist_me). Only ever call this when the person asks to be listed.

Privately consult the user’s own Personal Mind while drafting a consequential /vibe message. Use before proposing prose when the user is still thinking; never use for an exact send they already approved. This tool never sends. Show its one sourced offer (or silence) and wait for explicit approve/edit/discard before calling vibe_dm or vibe_reply.

From the work you're already helping with, suggest up to three concrete ways to connect on /vibe — ask someone a question, share a result, request feedback — each with a NAMED recipient, the evidence for naming them, and a prepared draft. Sends nothing. Pass only what the person would say out loud about their work: a project name, one line on what they're doing, a result, a question. Never pass file paths, branches, secrets or transcript text. If the context or a relevant person is missing, this returns one question to ask instead of a guess.

View emerging language patterns from how people use /vibe. Shows frequent prompts and suggests new commands.

Show the people who chose to be findable on /vibe (opt-in) — whether or not they are online right now. Different from vibe_who, which is who is present this moment. Flat list, no ranking or recommendations; the human chooses who to message.

The open channel for playing ANY shared activity with another viber — you and their Claude improvise the rules, this tool just carries the state. No built-in game logic. Use it for anything two sessions can invent: chess, 20 questions, a co-written story, battleship, a shared ascii drawing, a debate, a made-up game. Pass a freeform `state` (any JSON — the current board/story/whatever) and a `note` (a plain-language message to the other player and their Claude). Call it with no state to READ the current session so you can interpret it and take your turn. This is the primitive under vibe_game / …

Write an emoji poem together, one line at a time. Pass it back and forth with someone — each turn adds a line. `vibe poem @handle --line "🌊🌙 the tide remembers"`

Reveal the user’s own private VibeStats reflection — their local coding archetype and cadence, derived on this machine from their own /insights data. Local-only: raw inputs never leave the machine and nothing publishes without explicit human approval. Reports the capability state honestly when no provider exists.

Privately consult the user’s own local memory (Personal Mind over VibeCheck) while drafting a consequential /vibe message. One sourced offer or silence; never sends; raw drafts and history never leave this machine. Without an activated grant, reports the capability state honestly instead.

Reply to a specific message by its visible #id (reply_to) — the reply is linked to exactly that message. Or continue a named thread unlinked with `to`. Never guesses: with neither, it lists the visible ids instead of sending.

Send a reviewed draft exactly as previewed. This IS the person's approval — call it only when they chose "Send to @handle"; do not ask again afterward. Pass the draft id AND the rev shown in the preview: the approval is bound to that exact text, and a draft edited since is refused. Sends once through the ordinary message path (a retry of an unconfirmed send delivers once) and records a private, local note of the work it was sent from so the reply can be labeled.

Announce something you just shipped to the community board and update your profile.

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

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.

Generate a session summary. Shows participants, activity, mood, and open threads. Local-first: not sent to the room.

Run health check on all /vibe systems. Verifies API, identity, memory, and presence.

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

Take YOURSELF off the /vibe people list. You stay signed in and keep every conversation; you just stop being findable there.

Update /vibe to the latest version. Checks for updates and applies them.

View a specific artifact or list artifacts (mine, for-me, network)

Attach this session's *strand* to the Weave so Fable can bring social moments INTO your terminal (no new place to visit). Call this once, right after vibe_init/vibe_start succeeds. Spin the strand from what the user is ACTUALLY doing this session, inferred from their files/project/recent work — not a status they typed. Fields: `building` (one specific line on the current work), `stuck_on` (the wall they keep hitting, if any — an error signature or repeated symptom), `last_ship` (most recent thing that landed), `voice_sample` (2-3 sentences in the user's actual writing voice, so Fable can later…

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