MCP.Market

Vibo MCP server

by chrischall·io.github.chrischall/vibo-mcp·v2.4.5·1 stars

Vibo (vibodj.com) MCP — plan & manage event music: timeline, songs, ideas, questions, guests

B75/100grade B
What users say
No reviews yet
Be the first
Safety scan
B75/100

not scanned yet

Adoption
Growing

1 stars157 downloads/wk

Reviews

Write one

Nobody has reviewed Vibo yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Vibo tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Vibo compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 45% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
157
more than 71% of 12,191 servers with a package

Release history: 14 versions in the registry since 2026-09-15, latest 2026-10-16, typically one every 2 days.

Install Vibo in Claude Code, Cursor or VS Code

Runs npx -y vibo-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add vibo-mcp -- npx -y vibo-mcp
Add to Cursor

What the publisher says

From the Vibo repository's README, as published. We do not edit it. Read it on GitHub

vibo-mcp

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.

Install

{
  "mcpServers": {
    "vibo": {
      "command": "npx",
      "args": ["-y", "vibo-mcp"],
      "env": {
        "VIBO_EMAIL": "you@example.com",
        "VIBO_PASSWORD": "your_password"
      }
    }
  }
}

Authentication

Choose one method:

The server boots without credentials; the config error only surfaces on the first tool call.

How it works

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.

Development

npm install
npm run build   # tsc + esbuild bundle → dist/
npm test        # vitest

License

MIT

Nothing above is checked by us. What we check is on the safety report.

Vibo: common questions

Is Vibo MCP server safe?
Mostly: it is graded B (75/100). Read the Vibo safety report
How do I install Vibo?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Vibo need an API key?
Yes. The registry entry asks for VIBO_PASSWORD, VIBO_ACCESS_TOKEN, VIBO_REFRESH_TOKEN.
Is Vibo maintained?
The last commit was 32 days ago (2026-10-03). The latest release is v2.4.5.
How does Vibo compare with other MCP servers?
safety score 75/100 (higher than 45% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers); downloads a week 157 (more than 71% of 12,191 servers with a package). Full comparison.

More from chrischall →