A
licenseA
qualityD
maintenanceEnables AI assistants to load, query, and manage iCalendar files with full CRUD operations and support for multiple calendars.
8
7 npm
MIT
supershift-mcp
by Zyrial96
Related Servers
Alternatives to supershift-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables reading, analyzing, creating, and managing Google Calendar events across multiple accounts through natural language, with features like meeting pattern analysis and scheduling preferences.2-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage calendars and tasks through natural language, supporting Google Calendar operations like event creation, availability checking, and smart scheduling. It features schedule analysis, task reminders, and meeting time recommendations to streamline productivity.-
- FlicenseNot gradedqualityDmaintenanceProvides AI assistants with intelligent access to Google Calendar data, enabling natural language queries about availability, upcoming events, schedule conflicts, and meeting summaries through context-aware calendar integration.-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to analyze log time data from various sources to summarize project health, employee performance, and client status.-
- FlicenseAqualityDmaintenanceProvides intelligent weekly schedule analysis from Google Calendar, including day-by-day breakdowns, workout suggestions, office day detection, and scheduling problem identification through natural language queries.4-
TDQS
C2.4/5.0
Scored across 35 tools
Disambiguation2/5
Many tools have overlapping purposes (e.g., multiple create and preview variants for different backends, multiple listing and status tools). An agent would struggle to distinguish between create_supershift_shifts, create_supershift_sqlite_shifts, and their from_text counterparts without careful reading.
Naming Consistency3/5
Naming is mostly snake_case but mixes verb_noun (list_shifts, create_shifts) with noun_phrases (shifts_on_date, shift_locations, free_days). Some tools have inconsistent patterns (e.g., summarize_by_period vs summarize_shifts).
Tool Count2/5
35 tools is excessive for a shift management server. Many tools are redundant (e.g., three create shifts variants, three preview tools) and others are niche (reverse engineering report, inspect APK). A more focused set of 10-15 tools would be sufficient.
Completeness2/5
The tool set lacks update and delete operations for shifts, which are essential for full lifecycle management. While it covers creation, reading, and various status checks, the absence of update/delete creates gaps that could cause agent failures.
Maintenance
ActivityInactive
ResponsivenessNo issues