A
licenseNot graded
qualityB
maintenanceA local MCP server that exposes your UPV academic calendar and PoliformaT data to MCP clients, enabling natural language queries for classes, deadlines, announcements, and materials.
MIT
DTU-Calendar-MCP
by PV-Bhat
Related Servers
Alternatives to DTU-Calendar-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that gives Claude Desktop access to school data from Studie+ (Danish school platform), enabling queries about schedules, homework, assignments, and files directly in chat.MIT
- AlicenseNot gradedqualityAmaintenanceA read-only MCP server exposing NTNU course data to LLM assistants, enabling course catalog search, teaching schedules, weekly timetables, grade statistics, and course comparison tools.1MIT
- AlicenseNot gradedqualityAmaintenanceMCP server exposing NTNU course data (search, schedules, grades, semesters) as tools for LLM agents.16 npmMIT
- FlicenseAqualityBmaintenanceAn MCP server that gives desktop AI apps access to your Waterloo LEARN courses, enabling listing courses, getting announcements, content, grades, and upcoming events through natural language.52-
- AlicenseNot gradedqualityAmaintenanceA read-only MCP server that exposes iCalendar feeds as queryable tools for LLM agents, enabling calendar event retrieval and filtering.MIT
TDQS
A3.8/5.0
Scored across 6 tools
Disambiguation4/5
Most tools have clearly distinct purposes: listing upcoming items, listing inferred deadlines, fetching single items, summarizing by course, showing cache changes, and reporting feed status. The only potential confusion is between list_upcoming and list_deadlines, since deadlines are a subset of upcoming items, but the descriptions clarify the distinction.
Naming Consistency4/5
The naming pattern is mostly consistent verb_noun: list_deadlines, get_calendar_item, get_course_overview, get_calendar_changes, get_feed_status. list_upcoming deviates slightly because 'upcoming' is an adjective rather than a noun object, but the pattern is otherwise uniform and predictable.
Tool Count5/5
Six tools is well-scoped for a calendar-oriented MCP server. Each tool addresses a distinct need: browsing upcoming items, filtering deadlines, retrieving details, summarizing by course, detecting changes, and checking feed health. No tool feels redundant or unnecessary.
Completeness5/5
The tool surface covers the apparent read-only calendar domain well: listing upcoming content, surfacing deadlines, retrieving individual items, summarizing by course, tracking changes over time, and reporting cache/source status. There are no obvious missing operations that would create dead ends for an agent.
Maintenance
ActivityMaintained
ResponsivenessNo issues