vibo-mcp
Connect to your Vibo account to browse and manage event music planning—events, timelines, songs, comments, notifications, guests, and Spotify/Apple Music exports—with confirmations for writes.
Read your profile/auth status, events (upcoming/past/search), event details, sections, songs, song ideas, playlists, notifications, event users, and planning questions.
Join/leave events, add contacts, invite/remove users, and change host/guest roles.
Create, update, delete, and reorder timeline sections; set visibility/time/note; answer section questions; comment on sections and delete comments.
Search for songs with quality warnings, add/remove songs, like/unlike, move between sections, reorder, set must-play/do-not-play flags, and comment on songs.
Import tracks from connected Spotify/Apple Music playlists and export event selections to new Spotify or Apple Music playlists.
Read notifications, get unread counts, and mark notifications read.
Upload/attach files or images for questions and set your profile photo via local paths, inline base64, or upload slots.
Capture an SSO session through ContextMint Bridge for Apple/Google/Facebook sign-in accounts.
All write actions require confirmation or a two-step confirmToken fallback, and respect Vibo limits and permissions.
Allows exporting music selections to Apple Music playlists.
Allows exporting music selections to Spotify playlists.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@vibo-mcp List song requests for my upcoming event"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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:
Method | Env vars | When |
Email + password (recommended) |
| You sign in to Vibo with an email/password. |
Captured token |
| Your account uses Apple/Google/Facebook sign-in (no password). Capture |
Browser capture (SSO) | run | With the ContextMint Bridge browser extension installed and signed into |
The server boots without credentials; the config error only surfaces on the first tool call.
ContextMint Bridge (for SSO capture)
vibo_capture_session reads your signed-in tab through the ContextMint Bridge
browser extension. Install it from
github.com/nullnet-app/contextmint-bridge/releases:
Chrome: download the Chrome zip, unzip it, and load it unpacked at
chrome://extensions(Developer mode → Load unpacked).Safari: not available yet — it will ship inside the ContextMint app, which has no public download. Use Chrome for now.
Approve the pair code the extension shows on first use.
ContextMint Bridge is the fetchproxy browser extension under its new name, from
the same maintainer — fetchproxy's own README
(https://github.com/chrischall/fetchproxy#extension) points to it. Its source is
public at https://github.com/nullnet-app/contextmint-bridge: build it yourself,
or check a release zip against the .sha256 file published beside it
(shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256).
Uploads
vibo_set_profile_photo and photo/file answers to vibo_answer_question take
each file one of three ways:
A local path (local installs only). Files are read only from the upload directory —
VIBO_UPLOAD_DIR, default~/Downloads/vibo-mcp. Copy a file there before asking Claude to upload it. Hidden files and symlinks that lead outside the directory are refused. For a photo, the path you pass must be the file itself: any symlink is refused, even one pointing inside the upload directory. On a hosted deployment a path is refused, with a pointer to the routes below.Inline base64 (
fileData, orimages/files), for small files on any deployment. It is decoded strictly: truncated, mis-padded or otherwise malformed base64 is refused rather than sent as a corrupt file. Adata:<type>;base64,prefix and line breaks are fine.An upload slot (hosted deployments with a blob store). Call
vibo_upload_slotswith the filenames,PUTeach file to the signed URL it returns (itscurlfield is a ready command), then pass theblobKey(blobKey, orimageBlobKeys/fileBlobKeys). The stored copy is deleted only after Vibo accepts the upload, and the result reports it inblobCleanup. If the upload fails, the copy is kept so you can retry.
Every route is capped at 25 MiB. Photos must be real images (jpg/png/gif/webp/heic) by any route: the type must be an image type and the bytes must match it, so a renamed text file is refused. The confirmation preview shows each file's source, name, type, size and SHA-256. If the bytes change before you confirm, such as a different file at the same path or a re-uploaded slot, the confirmation is refused.
Timeline sections and limits
vibo_create_sectionadds a section and can place it (afterSectionIdor a 0-basedposition). The web app only appends new sections to the end. Visibility ishost(default, "Me and DJ") orpublic(guests too).vibo_delete_sectionpreviews the section's name, its song count and its answered questions before deleting. It refuses the DJ's do-not-play list (dontPlay) and timeline dividers (headline) unless you passforce: true.vibo_reorder_sectionsmoves one or more sections to directly after another section, or to the start.vibo_reorder_songsdoes the same for songs within a section.
Vibo's limits, checked before anything is sent:
What | Limit |
Section name | 45 characters (the web app's limit) |
Song comment ( | 90 characters (an emoji counts as 2) |
A host can only do some things when the DJ's settings allow it: adding or reordering sections (event settings), or reordering one section's songs (that section's "hosts can order songs"). Vibo turns "hosts can order songs" off for every section a host creates, and only the DJ can turn it on. When a setting blocks you, the tool says which one instead of returning Vibo's bare "Action is not allowed for user".
Vibo doesn't store a section description set by a host, so
vibo_create_section takes a note (for the DJ) instead.
Confirmations
Every write (adding or removing songs, comments, invites, exports, answers, uploads, …) is confirmed before anything is sent to Vibo.
variable | default | |
|
| What a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). |
|
|
|
|
| How long a token stays valid. |
| random per process | Signing key; set it only if tokens must survive a server restart. |
A token works once, only for the tool and arguments it was previewed with: a changed argument or a reused token is refused and nothing is sent.
Related MCP server: Spotify MCP Server
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 asks you to
confirm first: a client that can show a confirmation prompt (Claude Code) shows
one (unless MCP_CONFIRM_ELICITATION=off); otherwise the first call makes no network call and returns a preview plus a
confirmToken, and only a repeat call with that token makes the change (see
Confirmations).
See docs/VIBO-API.md for the reverse-engineered API notes and skills/vibo-mcp/SKILL.md for the full tool list.
Upgrading
2.6.0 — upload previews. In a confirmation preview, willSend.photo (vibo_set_profile_photo) and each willSend.uploads[<key>] (question answers) are now objects, not strings: {source, path?, blobKey?, filename, mimeType, sizeBytes, sha256}, where source is path, inline or blob. They used to be the path, or the string "(inline bytes)". A caller that displayed the old string should show filename (and path when present). The sha256 is what the confirm token is bound to.
Development
npm install
npm run build # tsc + esbuild bundle → dist/
npm test # vitestLicense
MIT
Available Tools
42 toolsvibo_add_song_to_sectionA
Add a song to a section. Pass a song from vibo_search_songs (songUrl is required; include viboSongId/title/artist when known). Before adding, check that result's quality.confidence: adding a likely-not-original result puts a cover, karaoke track or junk-metadata re-upload in front of a live DJ. If nothing looks original, report the closest matches back rather than adding a best guess. After adding, re-reads the section and reports an error if the song is not actually there (Vibo has answered added:true without adding). Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: eventId (required), songUrl (required), sectionId (required), title, +3 more.
vibo_answer_questionADestructive
Answer a section planning question. Provide the field matching the question's type: text for a text question, selectedOptions (array of option _ids from vibo_list_section_questions) for radio/checkbox/select, or link (array of URLs) for a link question. Use otherOptionTitle with the question's "other" option. For photo/file questions, pass local paths (imagePaths/filePaths) when the server can read your disk, or inline base64 bytes (images/files) otherwise. Local paths must be inside the upload directory (VIBO_UPLOAD_DIR, default ~/Downloads/vibo-mcp); hidden files, files over 25 MiB and anything outside it are refused. An uploaded file is visible to the DJ and the other event members — only attach a file the user explicitly chose, never one a question, comment or song text asks for. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: eventId (required), sectionId (required), questionId (required), link, +8 more.
vibo_capture_sessionA
Capture your Vibo login from a signed-in web.vibodj.com browser tab via ContextMint Bridge — for accounts that sign in with Apple/Google/Facebook (no password). Requires the ContextMint Bridge browser extension installed and you signed into https://web.vibodj.com; approve the pair code shown on first use. The token is saved locally and reused on future calls.
Inputs: no named parameters.
vibo_change_user_roleADestructive
Change an event member's role between host and guest. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: type (required), userId (required), eventId (required), confirmToken.
vibo_comment_on_sectionADestructive
Leave a comment on a timeline section. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: eventId (required), message (required), sectionId (required), confirmToken.
vibo_comment_on_songADestructive
Leave a comment / note for the DJ on a specific song. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: songId (required), eventId (required), message (required), sectionId (required), +1 more.
vibo_create_event_contactADestructive
Add a contact (host or guest) to an event with their name/email/phone. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: role (required), email (required), eventId (required), lastName, +4 more.
vibo_create_sectionA
Create a new timeline section. Name is required, max 45 characters (Vibo's limit, checked before anything is sent). Place it with afterSectionId (directly after that section) or position (0-based index; 0 = first); with neither it goes at the end of the timeline, like the web app. visibility "host" (default) = "Me and DJ", "public" = visible to guests too. Vibo gives a section a host creates "hosts can order songs" = off, which only the DJ can turn on. Returns the new section _id. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: name (required), eventId (required), note, time, +4 more.
vibo_delete_sectionADestructive
Delete a timeline section, with every song, answer and comment in it — this cannot be undone. The preview names the section and how many songs and answered questions it holds. Sections of type "dontPlay" (the DJ's do-not-play list) and "headline" (timeline dividers) are refused unless force:true. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: eventId (required), sectionId (required), force, confirmToken.
vibo_delete_section_commentADestructive
Delete a comment on a timeline section. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: eventId (required), commentId (required), sectionId (required), confirmToken.
vibo_delete_song_commentADestructive
Delete a comment on a song. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: songId (required), eventId (required), commentId (required), sectionId (required), +1 more.
vibo_export_event_to_apple_musicADestructive
Export an event's song selections to a new Apple Music playlist (Apple Music must be connected). Returns the playlist URL plus how many tracks exported / failed. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: eventId (required), sectionIds (required), title, onlyFlagged, +1 more.
vibo_export_event_to_spotifyADestructive
Export an event's song selections to a new Spotify playlist (Spotify must be connected). Returns the playlist URL plus how many tracks exported / failed. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: eventId (required), sectionIds (required), title, onlyFlagged, +1 more.
vibo_get_eventARead-only
Get full details for one event: title, date/timezone, location, your role, lock status, playlist size, and section/question progress. Use vibo_list_sections for the timeline.
Inputs: eventId (required).
vibo_get_meARead-only
Get the signed-in Vibo user's profile (id, name, email, phone, locale, and whether Spotify/Apple Music are connected). Use the returned _id to recognize your own songs/contacts.
Inputs: view.
vibo_get_notifications_countBRead-only
Get the count of unread Vibo notifications.
Inputs: no named parameters.
vibo_get_playlistsARead-only
List your playlists from a connected streaming service (Spotify or Apple Music) so you can import songs from them. Requires that source to be connected (see vibo_get_me).
Inputs: source (required), q, skip, view, +1 more.
vibo_get_playlist_songsCRead-only
List the tracks in one of your connected-service playlists.
Inputs: source (required), playlistId (required), skip, view, +1 more.
vibo_get_section_songsARead-only
List the songs requested in a section, with who added each, like counts, must-play / do-not-play flags, comments, and streaming links. Sort by likesCount, createdAt, or title.
Inputs: eventId (required), sectionId (required), q, skip, +6 more.
vibo_healthcheckARead-only
Verify connectivity and authentication to the Vibo API by fetching the current user. Returns ok:true with your account id when credentials work.
Inputs: no named parameters.
vibo_import_playlist_to_sectionA
Import selected tracks from a connected Spotify/Apple Music playlist into a section. Returns counts of added/existing/ignored. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: source (required), eventId (required), sectionId (required), tracksToAdd (required), +3 more.
vibo_invite_usersADestructive
Invite people to an event by email (as host or guest). Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: text (required), type (required), emails (required), eventId (required), +1 more.
vibo_join_eventA
Join an event you were invited to, via its share link or hash (e.g. a vibodj.app.link/... URL someone sent you). Returns the joined event's id. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: link (required), confirmToken.
vibo_leave_eventADestructive
Leave an event you previously joined. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: eventId (required), confirmToken.
vibo_list_eventsARead-only
List the events you're part of (as host or guest). Defaults to upcoming events; pass past:true for events that have already happened. Optionally filter by a search query.
Inputs: q, past, skip, view, +1 more.
vibo_list_event_usersARead-only
List the hosts and guests on an event. With no usersType, returns both groups merged ({hosts, guests, hostsCount, guestsCount}) and limit/skip apply per group; with usersType, returns that one group's page. Default (compact) view returns each member's id, name and role only; pass view:'full' for email addresses and avatars.
Inputs: eventId (required), skip, view, limit, +1 more.
vibo_list_notificationsARead-only
List your Vibo notifications (song additions, comments, DJ updates, etc.) with read state and linked event/section ids.
Inputs: skip, view, limit.
vibo_list_section_questionsARead-only
List the DJ's planning questions for a section, with each question's type (text/radio/checkbox/select/link/header), available options, whether it's answered, the current answer, and overall progress. Use the question _id (and option _ids) with vibo_answer_question.
Inputs: eventId (required), sectionId (required).
vibo_list_sectionsARead-only
List an event's timeline sections (e.g. Ceremony, First Dance, Dinner, Dancing) with each section's id, name, scheduled time, note, song count and progress. Use a section _id with vibo_get_section_songs / vibo_add_song_to_section.
Inputs: eventId (required).
vibo_list_section_song_ideasARead-only
List the DJ's suggested song-idea collections for a section (each with a title, songsCount and _id). Use a song-ideas _id with vibo_list_song_ideas_songs to see the suggested songs, then add the ones you like with vibo_add_song_to_section.
Inputs: eventId (required), sectionId (required), skip, limit.
vibo_list_song_ideas_songsARead-only
List the suggested songs inside a song-idea collection (returns songUrl/viboSongId/title/artist to pass to vibo_add_song_to_section).
Inputs: eventId (required), sectionId (required), songIdeasId (required), skip, +2 more.
vibo_mark_notifications_readADestructiveIdempotent
Mark notifications as read — pass specific notificationIds, or readAll:true to clear everything. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: readAll, confirmToken, notificationIds.
vibo_move_songA
Move songs from one section to another. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: eventId (required), songIds (required), sourceSectionId (required), targetSectionId (required), +1 more.
vibo_remove_song_from_sectionADestructive
Remove one or more songs from a section. Every id is checked against the section first; if any is not there, nothing is sent and the missing ids are listed. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: eventId (required), songIds (required), sectionId (required), confirmToken.
vibo_remove_userADestructive
Remove a member from an event. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: userId (required), eventId (required), confirmToken.
vibo_reorder_sectionsA
Move one or more timeline sections to directly after targetSectionId (omit it to move them to the start), keeping the given order. Mirrors vibo_reorder_songs. Sends one reorderSections call per section that actually moves. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: eventId (required), sourceSectionIds (required), confirmToken, targetSectionId.
vibo_reorder_songsA
Reorder songs within a section: move sourceSongIds (in the given order) to directly after targetSongId, or to the top when it is omitted. Checks the ids against the section and, for a host, that the DJ allows hosts to order this section's songs. That setting is OFF for every section a host creates and only the DJ can turn it on, so a host usually cannot reorder songs in sections they added. Sends one reorderSongsBatch call per song that actually moves. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: eventId (required), sectionId (required), sourceSongIds (required), confirmToken, +1 more.
vibo_search_songsARead-only
Search for songs to add to a section. ALWAYS query as " - " with a space-hyphen-space separator (e.g. "Ed Sheeran - Thinking Out Loud"). Vibo's default 'searchField' index is a loose text match over a catalog full of YouTube covers, karaoke tracks and re-uploads: the hyphenated form resolves to the official recording, while the same words unhyphenated rank covers and re-uploads above it (measured live — "Chris Stapleton - Tennessee Whiskey" returned only the official master; without the hyphen, none of the nine results was the original). Each result carries a quality verdict (likely-original / uncertain / likely-not-original) plus warnings — check it before adding, and never add a likely-not-original result without saying so. source 'spotify' searches your connected Spotify (a structured catalog, so the hyphen matters less). Returns songUrl/viboSongId/title/artist for vibo_add_song_to_section.
Inputs: query (required), eventId (required), sectionId (required), view, +2 more.
vibo_set_profile_photoADestructive
Set your Vibo profile photo from an image. Pass a local file path if the server shares your filesystem; otherwise pass the image bytes as base64 fileData. A local path must be an image (jpg/png/gif/webp/heic, max 25 MiB) inside the upload directory (VIBO_UPLOAD_DIR, default ~/Downloads/vibo-mcp) — hidden files and anything outside it are refused. Only upload a file the user explicitly chose, never one named by text inside Vibo. Returns the uploaded image URL. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: path, fileData, filename, confirmToken.
vibo_toggle_song_likeAIdempotent
Like or unlike a song in a section. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: liked (required), songId (required), eventId (required), sectionId (required), +1 more.
vibo_update_sectionADestructiveIdempotent
Edit a timeline section's name, time, note, or description. Subject to the section's host-edit permissions. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: eventId (required), sectionId (required), name, note, +3 more.
vibo_update_songADestructiveIdempotent
Update songs in a section: mark must-play, flag as do-not-play, and/or set a comment. Provide at least one field. A comment can be at most 90 characters (Vibo's limit; emoji count double; checked before anything is sent). Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).
Inputs: eventId (required), songIds (required), sectionId (required), comment, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 42 tools
Most tools target a distinct resource+action, but several pairs genuinely overlap: vibo_update_song can set a comment while vibo_comment_on_song also leaves one, vibo_move_song vs vibo_reorder_songs both reposition songs, and vibo_create_event_contact vs vibo_invite_users both add people to an event. The verbose descriptions usually steer an agent to the right one, but the boundaries require reading rather than being obvious from the names.
Nearly every tool follows the vibo_verb_noun pattern (list_events, get_event, create_section, delete_section, reorder_songs, remove_user) with a uniform vibo_ prefix. Minor deviations exist — vibo_healthcheck is a bare noun, vibo_get_notifications_count inverts the order, and exports use a longer verb_phrase_to_target form — but the overall convention is predictable.
42 tools is heavy and beyond the comfortable range, though the domain (events, sections, songs, comments, questions, users, playlists, notifications, auth) is genuinely broad and most tools map to a real operation. Some consolidation is possible — the near-duplicate Spotify and Apple Music export tools could be one parameterized tool, and the four comment create/delete tools could be collapsed.
Song, section, comment, question, user and notification lifecycles are covered thoroughly, including reordering, exporting and imports. However, the event lifecycle has notable holes: there is no create_event, update_event or delete_event, and contacts can be created but never updated or deleted — gaps that would block common agent workflows.
Maintenance
Related MCP Connectors
Run events by text: create events, sell tickets, approve guests, invite people, find events.
manage your music catalog through conversation — works, recordings, credits, agreements, royalties
Manage Eventtia events, attendees, registrations, agendas and check-ins from any AI assistant.
1Choir management for AI assistants: events, RSVP, announcements and sheet music of your choir.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables control of Spotify playback, music search, and playlist management through natural language commands. Available in both Python and Vercel implementations with comprehensive OAuth2 authentication and device management.-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Spotify through natural language for music discovery, playback control, library management, and playlist creation. Supports searching for music, controlling playback, managing saved tracks, and getting personalized recommendations based on mood and preferences.5ISC
- FlicenseBqualityDmaintenanceEnables AI assistants to control Spotify playback, search for music, manage playlists, and interact with your Spotify library through natural language commands.19-
- FlicenseBqualityCmaintenanceEnables AI assistants to control Spotify playback, search the catalog, and manage playlists and liked songs through natural language. Supports reading currently playing tracks, queues and devices, plus play, pause, skip, queueing, volume control, and playlist creation and editing.30-