Uses GitHub for secure authentication and identity persistence via OAuth, enabling developers to maintain a consistent handle and social profile across different editors and sessions.
/vibe MCP Server
The social layer for AI coding. DMs, presence, discovery, and games between developers — without leaving your editor.
Works with Claude Code, Cursor, VS Code, Windsurf, Cline, Continue.dev, JetBrains, and any MCP-compatible client.
Install
Add to your MCP config and restart your editor:
Add to ~/.claude.json:
Or via CLI:
Add to ~/.cursor/mcp.json:
Add to .vscode/mcp.json in your workspace:
Or add to your settings.json:
Add to ~/.codeium/windsurf/mcp_config.json:
Open Cline > MCP Servers icon > Configure > Edit JSON, then add:
Create .continue/mcpServers/vibe.json:
Go to Settings > Tools > AI Assistant > Model Context Protocol (MCP) and add a new server:
Command:
npxArguments:
-y slashvibe-mcp
Or import from your Claude Code config if you already have one.
Getting Started
Once installed, tell Claude:
That's it. Claude will authenticate you via GitHub, show who's online, and check your inbox.
If you prefer step-by-step:
Authenticate —
vibe initopens GitHub OAuth in your browser. Takes 30 seconds.See who's around —
vibe whoshows online builders and what they're working on.Check messages —
vibe inboxshows unread DMs.Send your first message —
vibe dm @seth hey, just set up /vibe!
Tools
Core — Messaging & Presence
Tool | What it does |
| Entry point — authenticates, shows who's online, checks inbox |
| Set up your identity via GitHub OAuth |
| See who's online and what they're building |
| Send a direct message |
| Check your unread messages |
| Open a conversation thread with someone |
| Send a quick wave to someone |
| React to a message |
| Set your mood or what you're working on |
| Set yourself away or return |
| End your session |
Discovery — Find Your People
Tool | What it does |
| Find builders by interests, projects, or activity |
| Get tag suggestions for your profile |
| Browse and offer skills |
| Find a learning partner |
| Generate an invite link |
Creative — Ship & Share
Tool | What it does |
| Announce what you shipped |
| Share an idea with the community |
| Ask the community for help |
| See what people are shipping and sharing |
| Create a shareable guide, workspace, or learning |
| View shared artifacts |
Memory — Context That Persists
Tool | What it does |
| Save a note about someone for next time |
| Pull up everything you know about someone |
| Delete a memory |
| Create an AIRC context handoff for another tool |
Games — 27 Multiplayer & Solo Games
Tool | What it does |
| Start a multiplayer game with someone |
| Play a solo game (riddles, hangman, number guess) |
| Challenge someone to tic-tac-toe |
| Collaborative crossword puzzle |
| Collaborative ASCII drawing |
| Start a party game for 3+ players |
Bridges — Cross-Platform Social
Tool | What it does |
| Check your X/Twitter mentions |
| Reply on X from the terminal |
| Unified inbox across platforms |
| Post to multiple networks at once |
Diagnostics
Tool | What it does |
| Full health check — API, auth, storage, presence |
| Quick connection and identity test |
| Show available commands |
| Check for and apply updates |
| Configure preferences |
How It Works
/vibe is an MCP server that connects your editor to slashvibe.dev. Messages sync via a Postgres backend with local SQLite persistence for offline-first speed. Everyone using /vibe is on the same network — regardless of which editor they use.
Identity persists via GitHub OAuth — your handle follows you across sessions
Messages are stored locally first, then synced to the server (optimistic send)
Presence broadcasts via heartbeat — others see you in real time
Memory is local — notes you save about people stay on your machine
Troubleshooting
"I installed but don't see /vibe tools in Claude Code"
Make sure you restarted Claude Code after adding the MCP config
Check your config file:
~/.claude.jsonor~/.config/claude-code/mcp.jsonRun
vibe doctorto diagnose issues
"Authentication failed or timed out"
The OAuth flow opens a browser window — if it didn't open, go to slashvibe.dev/login manually
The auth callback runs on
localhost:9876— make sure that port is freeYou have 2 minutes to complete the GitHub login
"Messages aren't sending"
Run
vibe doctorto check API connectivityCheck your internet connection
Messages are saved locally even if the API is down — they'll sync when you reconnect
"I see 'Unknown tool' errors"
You may be running an older version. Run
vibe updateor reinstall:npm install -g slashvibe-mcp
Configuration
Config lives at ~/.vibecodings/config.json (primary) or ~/.vibe/config.json (legacy fallback).
Local message database: ~/.vibecodings/sessions.db (SQLite, shared with Vibe Terminal desktop app).
Contributing
We welcome contributions. Please read our Contributor License Agreement before submitting pull requests.
Report bugs via GitHub Issues
Propose features via Discussions
License
MIT — see LICENSE
Links
slashvibe.dev — The platform
Vibe Terminal — Desktop app
@slashvibe on X — Updates
Built by Slash Vibe, Inc.