Vibo (vibodj.com) MCP — plan & manage event music: timeline, songs, ideas, questions, guests
MCP server for Vibo (vibodj.com) — plan your event music as a host/couple. Browse your events and timeline, see and add song requests, like songs, manage notifications, and export selections to Spotify/Apple Music, all via natural language.
Developed and maintained by AI (Claude Code). Use at your own discretion. Unofficial — not affiliated with Vibo. Works only with your own account/data.
{
"mcpServers": {
"vibo": {
"command": "npx",
"args": ["-y", "vibo-mcp"],
"env": {
"VIBO_EMAIL": "you@example.com",
"VIBO_PASSWORD": "your_password"
}
}
}
}
Choose one method:
| Method | Env vars | When |
|---|---|---|
| Email + password (recommended) | VIBO_EMAIL, VIBO_PASSWORD | You sign in to Vibo with an email/password. |
| Captured token | VIBO_ACCESS_TOKEN (+ VIBO_REFRESH_TOKEN) | Your account uses Apple/Google/Facebook sign-in (no password). Capture x-token/x-refresh-token from a signed-in web.vibodj.com session. |
| Browser capture (SSO) | run vibo_capture_session | With the fetchproxy browser extension installed and signed into web.vibodj.com, capture the token automatically (saved to ~/.vibo-mcp/session.json). |
The server boots without credentials; the config error only surfaces on the first tool call.
Vibo's app talks to a GraphQL API at https://api.vibodj.com/v2/graphql,
authenticating with an x-token header obtained from an email/password
signIn. This server reuses that same flow server-side (no browser needed) and
wraps the host/couple operations as MCP tools. Every mutating tool is
confirm-gated: without confirm: true it returns a dry-run preview and makes no
network call.
See docs/VIBO-API.md for the reverse-engineered API notes and skills/vibo-mcp/SKILL.md for the full tool list.
npm install
npm run build # tsc + esbuild bundle → dist/
npm test # vitest
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y vibo-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-chrischall-vibo-mcp": {
"command": "npx",
"args": [
"-y",
"vibo-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencevibo-mcpnpmio.github.chrischall/vibo-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.