No user-submitted related servers found.
Scored across 25 tools
Most tools target distinct resources and actions, and descriptions clarify ambiguous boundaries (e.g., scheduling vs moving vs assigning contributions). Minor overlap remains between get_event's optional sub-lists and dedicated list tools, and between timetable movement and update operations, but these are manageable.
All tools use the consistent indico_ prefix and snake_case verb_noun pattern (e.g., indico_create_event, indico_list_contributions). The only slight outlier is indico_whoami, but it remains readable and does not disrupt the overall convention.
With 25 tools, the surface is heavy for an MCP server, exceeding the typical 3-15 sweet spot. While each tool maps to a distinct operation in a complex event-management domain, the total risks overwhelming agents and could likely be consolidated.
Core workflows for events, sessions, contributions, timetable, and registration are covered, but explicit delete operations for events, sessions, and contributions are missing (deletion is only partly folded into unschedule behavior). Single-resource getters for sessions, contributions, and session blocks are also absent, creating notable lifecycle gaps.