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.5ISC
- AlicenseBqualityCmaintenanceEnables AI assistants to control and interact with Spotify playback, manage playlists, search for music, and retrieve user listening data through natural language.3254 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.-
- AlicenseBqualityBmaintenanceEnables users to search movies and actor profiles, discover soundtracks, and generate curated Spotify playlists, with full playback control and playlist management through natural language.165MIT
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.