slashvibe-mcp

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.

Install

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.

It works from your own terminal or when your coding agent runs it for you. (The bare npx slashvibe-mcp is what a coding agent launches as the server; without a terminal it installs nothing and says so.)

What it is like

Something arrives. You are mid-task. After the next tool call your agent says:

@lab_a wrote you: "we split it: local decides when, cloud decides where. how did you
stop local becoming the decider when cloud is slow?"

Draft reply, from what you're working on:
  we tried that split and it collapsed. what fixed it: cloud owns the whole decision,
  local only reports capacity, plus a short lease only cloud can grant.

Send · Edit · Cancel

You did not open an inbox and you did not write the answer. Nothing was sent, and nothing was marked read, until you chose.

Something leaves. Type /vibe. Your agent finds the question or the result in the session, picks the person it is for, writes it, and shows you the exact message. Send, Edit or Cancel. Or just say it: message @sam: ship it.

Who's here

When you open a session, one line tells you which of the people you know are around:

/vibe · here now: @sam (retry queue for webhook delivery, door open) · @ada (local or cloud)

That is a buddy list, on purpose. /vibe is multiplayer: the point is the people.

• It names only people you know: someone you have written to, or opened a line with. Never a stranger, never an agent, never someone you muted.
• It appears once, when you sit down. Nothing interrupts you to say someone came or went.
• What each person says they are working on is the line they set themselves.
• quiet hides it along with everything else.

npx slashvibe-mcp invisible        # be here without showing as here · undo: visible

Invisible, your sessions stop saying you are here, so you drop off other people's lists within about ten minutes. You still see who is here, and messages still reach you.

A door

Not everything is a message. If you are building something people can open, leave a door:

npx slashvibe-mcp door https://your-project.dev "Retry Lab: drag the slider"
npx slashvibe-mcp door share       # leave it with the people you know · take it down: door close

Now the people you left it with see it beside your name, and any of them can say visit @you:

🚪 Visiting @sam: "Retry Lab: drag the slider, watch 10,000 webhooks back off"
   sam-retries.vercel.app · opened in your browser
   @sam is here now, working on: "retry queue for webhook delivery"

You are a visitor. Nothing was sent, and @sam was not told.
Say something to @sam · or just look around

• A door is not published. It goes, as one message each, only to people you have already written to or opened a line with. Anyone else has nothing to see.
• Only you can set or share your door, from your terminal. No tool can.
• Public https links only. A visit opens the link in the visitor's own browser; /vibe never fetches it, and you are not told who came.

An open line

With someone you trust, you can go one step further. Open a line, from your terminal:

npx slashvibe-mcp trust @ada      # close it: untrust @ada · see them: lines

The command checks that you are signed in and that @ada exists, and tells you who that is before it opens the line; a handle /vibe does not know opens nothing.

After that your age

... View full README on GitHub