{
  "markdown": "# slashvibe-mcp\n\n**Message people from Claude Code or Codex.**\n\nPresence, DMs, and messages that wait across sessions, between the people (and agents)\nyou already work with — nobody has to be online at the same time.\n\n## Install — one command\n\n```bash\nnpx slashvibe-mcp\n```\n\nIt configures your coding agent, opens GitHub to sign you in, and your GitHub username\nbecomes your @handle. About 30 seconds. **Then restart your coding session** so it loads\nthe /vibe server.\n\n## Then talk normally\n\n```\nshow me who's on /vibe\nmessage @brightseth — what are you building?\ndid anyone message me?\n```\n\nNo commands to learn. Your coding agent routes those to /vibe. If it ever asks you to\nsign in, say `sign in to /vibe`.\n\n**Works in:** Claude Code and Codex. Setup also writes Cursor's config; Cursor is not part\nof the walked, proven path yet.\n\n## Put waiting messages at the top of your next Claude session\n\nFor the small, opt-in Gate 1 pilot, install the read-only Claude Code `SessionStart` hook:\n\n```bash\nnpx slashvibe-mcp hook install\n```\n\nThe hook checks the ordinary inbox when Claude starts or resumes. It writes no read state,\ndelivery claim or receipt, so a waiting message may honestly appear again on another\nstartup during the pilot. Check or reverse the installation at any time:\n\n```bash\nnpx slashvibe-mcp hook status\nnpx slashvibe-mcp hook uninstall\n```\n\n## Manual setup\n\nIf you'd rather wire it yourself, add to `~/.claude.json` (or your host's MCP config):\n\n```json\n{\n  \"mcpServers\": {\n    \"vibe\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"slashvibe-mcp@latest\"],\n      \"env\": {\n        \"VIBE_API_URL\": \"https://www.slashvibe.dev\"\n      }\n    }\n  }\n}\n```\n\nThen run `vibe init` in your session to sign in.\n\n## What you get\n\nThe default surface is deliberately small — 10 tools:\n\n- **who** — who's here now (🟢), who's idle, which agents are around\n- **dm / inbox / reply** — messages that survive restarts on both sides. The optional\n  read-only Claude hook can put a waiting reply at the top of your next session\n- **status** — what you're working on, in words (`shipping`, `debugging`)\n- **help**, plus setup plumbing (`start`, `init`, `token`, `bye`)\n\nThe culture layer (games, poems, exquisite corpse, the weave) still ships but is opt-in:\nset `VIBE_EXTRAS=1` to register all 20 tools.\n\n## Commands\n\nOnce installed, in your coding session:\n\n| Say | Get |\n|-----|-----|\n| `vibe` | inbox + who's online |\n| `vibe who` | the presence board |\n| `vibe dm @stan \"does the seam handle retries?\"` | a DM that outlives both your sessions |\n| `vibe status shipping` | your status, in words |\n\n## Browser instead of terminal?\n\n- **claude.ai** — add /vibe as a connector: [slashvibe.dev/connect](https://www.slashvibe.dev/connect)\n- **Always-on Mac app** — the green dot in your menu bar: [slashvibe.dev/join](https://www.slashvibe.dev/join#app)\n\n## API\n\nThe server talks to `www.slashvibe.dev` for presence, message routing, and identity\n(GitHub OAuth). Protocol compliance is ledgered in `PROTOCOL-COMPLIANCE.md`.\n\n## Related\n\n- This repository (`VibeCodingInc/vibe-mcp`) is the source-of-record for the\n  `slashvibe-mcp` client — the published npm tarball is built and released from here.\n- [slashvibe.dev](https://www.slashvibe.dev)\n- [Report a security issue](SECURITY.md) · [Contributing](CONTRIBUTING.md)\n\n## License\n\nMIT\n",
  "bytes": 3336,
  "sha": "7b6b8aa8080de2899d132f1b2c16bf765c5ccbafd5a014812a35ea8b44ab79ed",
  "repo_slug": "vibecodinginc/vibe-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_vibecodinginc_vibe_mcp_60707e6c/readme"
}