Log inSubmit server
Vibo MCP logo

Vibo MCP

Plan Vibo event music with MCP tools for timelines, requests, song organization, notifications, and playlist exports.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Vibo MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "vibo-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vibo-mcp"
      ],
      "env": {
        "VIBO_EMAIL": "YOUR_VALUE_HERE",
        "VIBO_PASSWORD": "YOUR_VALUE_HERE",
        "VIBO_ACCESS_TOKEN": "YOUR_VALUE_HERE",
        "VIBO_REFRESH_TOKEN": "YOUR_VALUE_HERE",
        "VIBO_UPLOAD_DIR": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_MODE": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_TTL_SECONDS": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_SECRET": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 42 tools correctly (Today).

Overview

The vibo-mcp MCP server connects AI assistants to Vibo’s event-planning account data through its GraphQL API. It lets hosts or couples browse events and timelines, manage song requests, organize sections and songs, handle notifications, and export selections to Spotify or Apple Music. Authentication supports Vibo email/password credentials, captured access tokens, or browser-based SSO capture. Reach for it when event music planning needs to be managed through natural-language MCP tools.

Use cases

  • Browse an event timeline
  • Manage song requests
  • Reorder sections and songs
  • Export selections to a music service
  • Update event questions and notifications

Key features

  • Vibo event and timeline access
  • Song request and like management
  • Timeline section and song ordering
  • Spotify and Apple Music exports
  • Confirmation-protected writes
  • Email, token, and browser-session authentication

Tools42

What Vibo MCP lets your agent do. Expand a tool for its parameters.

Verified live~12.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 48d

What it can do

From the 42 tools this server returned when we ran it; 42 declare their own safety hints.

Can delete or modify data · 18Writes files · 2Handles credentials · 28Makes network requests · 42Read-only tools · 24
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age136 days
Maintainers1

Observed 2026-10-30 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · vibo-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads2.7kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed42Callable tools this server registers over MCP.

How Vibo MCP works

What vibo-mcp MCP server does

The vibo-mcp MCP server exposes Vibo host and couple workflows through MCP tools. It works with the account’s events, timelines, song requests, notifications, event questions, invitations, profile photos, and music selections. It can also export selected songs to Spotify or Apple Music.

The toolset is intended for managing your own Vibo account and data. It is unofficial and is not affiliated with Vibo. Typical tasks include checking an event timeline, adding or removing requested songs, liking songs, updating song comments, arranging sections, and preparing playlist exports.

How it works

Vibo’s web application uses a GraphQL endpoint at https://api.vibodj.com/v2/graphql. The vibo-mcp MCP server authenticates on the server side and sends requests with the account’s Vibo token, so normal email/password use does not require a browser session.

Authentication can use VIBO_EMAIL and VIBO_PASSWORD, a supplied VIBO_ACCESS_TOKEN with an optional refresh token, or a session captured from a signed-in web.vibodj.com tab. Browser capture uses the ContextMint Bridge extension and saves the session at ~/.vibo-mcp/session.json.

All mutating operations require confirmation before data is sent. Clients with prompt support can show a normal confirmation request. On clients without that capability, the first call returns a preview and one-time token; a second call with the approved token performs the operation. Tokens are restricted to the original tool arguments and expire according to the configured TTL.

Setup and configuration

Add the server to an MCP client using npx -y vibo-mcp. Configure either the email/password pair or token-based authentication. The process can start without credentials, but the authentication error appears when the first tool is called.

Set VIBO_UPLOAD_DIR when controlling where local upload files are read; the default is ~/Downloads/vibo-mcp. Uploads reject hidden files, unsafe external symlinks, and files larger than 25 MiB. Photo uploads must contain valid image data matching their file type.

MCP_CONFIRM_MODE controls writes for clients that cannot display confirmation prompts. Its supported values are ask-user, auto, and refuse; the default is ask-user. MCP_CONFIRM_TTL_SECONDS defaults to 600 seconds, while MCP_CONFIRM_SECRET can provide a stable signing key across restarts.

Tools and capabilities

The vibo-mcp MCP server supports capabilities including:

  • Browsing events and timeline content.
  • Creating, deleting, and reordering timeline sections.
  • Reordering songs within sections when Vibo permissions allow it.
  • Adding, removing, liking, and commenting on songs.
  • Managing notifications, invitations, questions, and profile photos.
  • Exporting selections to Spotify or Apple Music.

Section names are limited to 45 characters, and song comments passed through the update operation are limited to 90 characters. Host permissions depend on the DJ’s event and section settings.

Limitations and notes

Vibo may block section or song reordering based on DJ-controlled settings. Hosts cannot override those restrictions through the server. New sections are appended by Vibo’s web application, although the tool can request placement using a position or following section. Host-created sections have song ordering disabled until the DJ enables it.

Deletion includes a preview of the section name, song count, and answered questions. The server refuses deletion of the DJ’s do-not-play list and timeline dividers unless force is supplied. A host-provided section description is not stored by Vibo, so the create-section operation records a note for the DJ instead.

The project is maintained as an unofficial integration and should be used with your own Vibo account and data.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Vibo MCP

vibo-mcp is an MCP server that connects AI assistants to Vibo’s event-planning GraphQL API and provides tools for browsing events and timelines, managing song requests, organizing songs and sections, handling notifications and questions, and exporting selections to Spotify or Apple Music.

Install it through an MCP client with the command `npx -y vibo-mcp`. Add the server with your chosen authentication environment variables, such as `VIBO_EMAIL` and `VIBO_PASSWORD`, in the client’s MCP configuration.

Use `VIBO_ACCESS_TOKEN` and optionally `VIBO_REFRESH_TOKEN`, or capture a signed-in browser session with the ContextMint Bridge extension. Browser capture reads the signed-in `web.vibodj.com` tab and saves the session locally.

Yes, every write requires confirmation before it is sent to Vibo. Clients with prompt support show a confirmation prompt; other clients use a preview and one-time confirmation token. `MCP_CONFIRM_MODE` controls behavior when a prompt cannot be displayed.

Yes, it can upload profile photos and photo or file answers from the configured local upload directory. Files must be within that directory, no larger than 25 MiB, and photo content must match the file’s image type.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewVibo MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/vibo-mcp?style=directory)](https://allmcps.com/mcp/vibo-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/vibo-mcp"><img src="https://allmcps.com/api/badge/vibo-mcp?style=directory" alt="Vibo MCP on AllMCPs" /></a>