vibo-mcp
Related Servers
Alternatives to vibo-mcp
No user-submitted related servers found.
Related Servers
- 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.52 npm5MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to control and interact with Spotify playback, manage playlists, search for music, and retrieve user listening data through natural language.3261 npmMIT
- 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-
- FlicenseBqualityDmaintenanceEnables AI assistants to control Spotify playback, search for music, manage playlists, and interact with your Spotify library through natural language commands.19-
- 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 gradedqualityBmaintenanceEnables users to search movies and actor profiles, discover soundtracks, and generate curated Spotify playlists, with full playback control and playlist management through natural language.1MIT
TDQS
Scored across 42 tools
Most tools have clearly distinct purposes (list vs get vs create vs delete for each resource). However, a few pairs overlap: vibo_update_song can set a comment while vibo_comment_on_song also comments on a song; vibo_create_event_contact and vibo_invite_users both add members; and vibo_healthcheck duplicates vibo_get_me's profile fetch. Descriptions mostly clarify these differences.
All 42 tools use the vibo_ prefix and consistent snake_case with verb_noun structure (e.g., vibo_list_events, vibo_create_section). No mixed conventions or camelCase. Highly predictable.
42 tools is well above the 25-tool threshold for 'too many' in the rubric. While the domain is rich, many granular operations (like/comment/delete comment, move/reorder) could be consolidated; the set feels heavy.
Song, section, comment, notification, user, and playlist workflows are well covered including create/update/delete. However, event creation, update, and deletion are absent, leaving a significant gap in event lifecycle management. Agents asked to create or edit an event would hit a dead end.