syllabus-calendar-mcp
Related Servers
Alternatives to syllabus-calendar-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables course discovery and registration planning using official UBC Academic Calendar and UBCGrades data, plus read-only personal Workday snapshot tools for section availability, schedules, and overlap checks.7AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to read exported WhatsApp school-group chats, surface events and doubtful amounts, dates, or times, check conflicts, and export confirmed events to an .ics calendar with reminders.MIT
- AlicenseBqualityBmaintenanceEnables users to query official undergraduate and graduate course schedules, indexes, prerequisites, and exam timetables, including tools for comparing indexes and finding matching schedules. It is read-only, local, and supports filtering by days, times, lesson types, teaching weeks, and schedule clashes.7220 PyPI1MIT
- AlicenseAqualityDmaintenanceEnables course planning for University of Pennsylvania by searching the catalog, inspecting sections and ratings, detecting schedule conflicts, and building weekly schedules.15MIT
- AlicenseAqualityAmaintenanceGives AI assistants direct, on-demand access to McGill's public Visual Schedule Builder timetable data, letting them search course offerings, fetch sections and meeting times, check conflicts, and generate ranked schedule combinations without a login, API key, or browser session. Queries and schedule calculations run locally on structured results, with a short-lived cache for repeated requests.46 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables natural-language queries across multiple schools' Canvas and Blackboard accounts for courses, notifications, assignments, grades, feedback, and schedules, with read-only access and local todo/calendar export.9MIT
TDQS
Scored across 4 tools
Each tool has a distinct role in the pipeline: parse text, build an .ics file, merge calendars, and preview recurring class dates. The only soft overlap is that build_ics internally expands recurring classes (holidays/reading weeks) while expand_recurring_classes exists as a separate preview step, so an agent could hesitate on which to use for recurrence handling.
All four names are snake_case and verb-first (extract_, build_, merge_, expand_), matching a clear verb_noun convention throughout. build_ics uses an acronym noun but still fits the same pattern.
Four tools map cleanly onto the parse → build → merge/preview workflow with no filler. The count is tight but each tool covers a necessary stage of the syllabus-to-calendar domain.
The core lifecycle is covered: text extraction, .ics generation with reminders and timezones, calendar merging with conflict detection, and recurrence expansion. Minor gaps exist around editing/inspecting existing events or importing an .ics for non-merge purposes, but the stated purpose is well served.