Vibe

You use the presence layer called vibe MCP Server to see who’s online, message builders, and share context directly from your editor. It integrates with multiple editors and provides a unified way to authenticate, discover online collaborators, and manage your messages and session context without leaving your development environment.

How to use

After you have the MCP server configured in your editor, you can start interacting with others right away. Start by authenticating with your GitHub identity, then explore who is online, check unread messages, and send quick messages to collaborators. You can share what you are working on, summarize sessions, and replay past work to collaborate more effectively.

How to install

Prerequisites: you need Node.js installed on your system. You also should have npm or npx available to install and run the MCP server integration.

npx slashvibe-mcp install

If you prefer to configure the MCP server manually for each editor, add the vibe server using the following examples and restart your editor after adding the config.

claude mcp add vibe -- npx -y slashvibe-mcp

{
  "mcpServers": {
    "vibe": {
      "command": "npx",
      "args": ["-y", "slashvibe-mcp"]
    }
  }
}

{
  "mcpServers": {
    "vibe": {
      "command": "npx",
      "args": ["-y", "slashvibe-mcp"]
    }
  }
}

Claude Code configuration

claude mcp add vibe -- npx -y slashvibe-mcp

Cursor configuration

{
  "mcpServers": {
    "vibe": {
      "command": "npx",
      "args": ["-y", "slashvibe-mcp"]
    }
  }
}

VS Code (GitHub Copilot) configuration

{
  "servers": {
    "vibe": {
      "command": "npx",
      "args": ["-y", "slashvibe-mcp"]
    }
  }
}

Windsurf configuration

{
  "mcpServers": {
    "vibe": {
      "command": "npx",
      "args": ["-y", "slashvibe-mcp"]
    }
  }
}

Cline / Continue.dev / JetBrains configuration

For Cline open MCP Servers > Configure > Edit JSON and add the vibe server as shown.

{
  "command": "npx",
  "args": ["-y", "slashvibe-mcp"]
}

Available tools

vibe_who

See who is online and what they are building.

vibe_status

Set your mood or your current work focus.

vibe_away

Mark yourself as away with a message.

vibe_back

Return from away status.

vibe_presence_agent

Run a background presence agent to keep your status updated.

vibe_dm

Send a direct message to another user.

vibe_inbox

Check unread messages in your inbox.

vibe_ping

Send a quick wave to someone.

vibe_react

React to a message in a conversation.

vibe_open

Open a conversation thread.

vibe_follow

Follow a user for notifications.

vibe_unfollow

Unfollow a user.

vibe_start

Entry point that authenticates, shows presence, and checks inbox.

vibe_bye

End your current session.

vibe_context

Share what you’re working on during a session.

vibe_summarize

Generate a session summary from your local journal.

vibe_session_resume

Resume context from a prior session.

vibe_session_save

Save your session with replayable context.

vibe_session_fork

Fork an existing session to extend work.

vibe_handoff

Hand off a task with full context.

vibe_discover

Find people, skills, and collaborators.

vibe_invite

Generate an invite link to collaborate.

vibe_remember

Save a note about someone for memory.

vibe_recall

Pull up everything you know about someone.

vibe_forget

Delete a memory about someone.

vibe_ship

Share what you shipped or request feedback.

vibe_feed

See what people are shipping.

vibe_reserve

Reserve files for editing to prevent conflicts.

vibe_release

Release file reservations.

vibe_reservations

List active reservations.

vibe_create_artifact

Create a shareable guide or workspace.

vibe_view_artifact

View shared artifacts.

vibe_init

Set up identity via GitHub OAuth.

vibe_help

Show available commands.

vibe_doctor

Health check for API, auth, storage, and presence.

vibe_update

Check for and apply updates.

vibe_settings

Configure preferences.

vibe_notifications

Configure notification channels.

vibe_mute

Mute a user.

vibe_report

Report issues or inappropriate behavior.