Vibe MCP Server

[DEPRECATED — see VibeCodingInc/vibe-platform mcp-server] Social MCP server — DMs, presence, and discovery for AI-assisted developers.

Local serverstdioGo

What is the Vibe MCP MCP server?

[DEPRECATED — see VibeCodingInc/vibe-platform mcp-server] Social MCP server — DMs, presence, and discovery for AI-assisted developers. That is what the vibe mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Social MCP server — DMs, presence, and discovery for AI-assisted developers. See who's building, message them, share what you shipped. Works with Claude Code, Cursor, VS Code, Windsurf, and any MCP client.

The tools it exposes

The server publishes 9 tools. What each one is for:

  • vibe_start — Entry point — authenticates, shows presence, checks inbox
  • vibe_init — Set up your identity (GitHub OAuth)
  • vibe_who — See who's online and what they're building
  • vibe_dm — Send a direct message
  • vibe_inbox — Check your unread messages
  • vibe_status — Set your mood (shipping, thinking, debugging, etc.)
  • vibe_ship — Share what you shipped
  • vibe_discover — Find people building similar things
  • vibe_help — Show available commands

Getting it running

slashvibe-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Vibe MCP's toolset — vibe_start, vibe_init, vibe_who and 6 more — is a fair guide to whether it matches your workflow. It is maintained by vibecodinginc; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Vibe MCP.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
vibe_startEntry point — authenticates, shows presence, checks inbox
vibe_initSet up your identity (GitHub OAuth)
vibe_whoSee who's online and what they're building
vibe_dmSend a direct message
vibe_inboxCheck your unread messages
vibe_statusSet your mood (shipping, thinking, debugging, etc.)
vibe_shipShare what you shipped
vibe_discoverFind people building similar things
vibe_helpShow available commands

How to install the Vibe MCP MCP server

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

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Vibe MCP to vibe start.
  • Use Vibe MCP to vibe init.
  • Use Vibe MCP to vibe who.

Frequently asked questions

It connects Vibe MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (vibe_start, vibe_init, vibe_who, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Vibe MCP directly.