F
licenseNot graded
qualityD
maintenanceEnables AI agents to search and access public calendar data, supporting iCal, CalDAV, and Google Calendar sources with event search, details, and availability checks.
-
indico-mcp
by vuillaut
Related Servers
Alternatives to indico-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to manage Microsoft 365 and Outlook calendars through the Microsoft Graph API. It supports comprehensive event operations including listing, creating, and updating meetings, as well as finding available slots across multiple attendees.-
- AlicenseAqualityCmaintenanceEnables AI assistants to search, filter, and analyze Microsoft events (conferences, workshops, webinars) using the Microsoft Events API.42MIT
- AlicenseAqualityBmaintenanceEnables creating and managing events on RealEvents, including listing public events, registering attendees, and updating event details, all from MCP-compatible AI assistants.688 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables LLM agents to read, schedule, update, and delete calendar events and tasks on a self-hosted CalDAV server, and to query availability for free/busy slots.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Google Calendar events, including reading, searching, creating, updating, and deleting events, as well as checking availability and listing calendars.18 npmMIT
TDQS
B3.4/5.0
Scored across 25 tools
Disambiguation4/5
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.
Naming Consistency5/5
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.
Tool Count3/5
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.
Completeness3/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues