No user-submitted related servers found.
Scored across 39 tools
Every tool targets a distinct operation on a specific resource (events, sections, songs, users, notifications). Even closely related tools like vibo_list_section_song_ideas vs vibo_list_song_ideas_songs or vibo_get_section_songs vs vibo_search_songs have clearly separated responsibilities.
All tools follow a consistent `vibo_<verb>_<noun>` pattern (e.g., list_events, get_event, add_song_to_section, remove_user). Minor one-word exceptions like vibo_healthcheck and vibo_get_me do not disrupt the overall predictable style.
With 39 tools, the surface is far larger than the typical well-scoped server (3–15 tools). While the domain is broad, the number feels unwieldy and could likely be consolidated without losing functionality.
The set covers many read and update operations but lacks fundamental event lifecycle tools—there is no way to create, update, or delete an event. Users can join/leave but not manage events they host, which is a major gap for an event planning service.