UofT Timetable Builder MCP
Related Servers
Alternatives to UofT Timetable Builder MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceLocal-first Rutgers course planning assistant that answers 'what should I take and when?' using a CP-SAT solver, real transcript data, and live SOC data, connected to Claude via MCP.13-
- AlicenseNot gradedqualityCmaintenanceMCP server for querying the public UCLA Schedule of Classes. It provides tools to list terms, subject areas, search courses, and get detailed enrollment, waitlist, and section information.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to operate training records, nutrition lookup, body-metric tracking, and web search through standard stdio tools.1MIT
- FlicenseNot gradedqualityDmaintenanceRemote MCP connector providing live, structured access to CMU Courses public data including courses, prerequisites, schedules, instructors, gen-eds, and final-exam times to help students plan schedules.-
- AlicenseNot gradedqualityCmaintenanceProvides MCP tools to fetch and filter schedules for groups, teachers, and rooms from VSUET's timetable site, with support for JSON or text output.MIT
- FlicenseNot gradedqualityDmaintenanceUnofficial MCP tools for LettuceMeet to create polls, view responses, and find meeting overlaps via CLI or MCP server.1-
TDQS
Scored across 10 tools
Most tools target distinct actions, but plan_timetable and save_timetable both create public share links, and the generic uoft_read/uoft_result discovery tools overlap conceptually with find_courses and course_info. An agent could reasonably hesitate between the specific domain reads and the generic batched-read interface.
All names use snake_case, but the set mixes a uoft_-prefixed auth/meta namespace (uoft_login, uoft_auth_status, uoft_read) with unprefixed domain tools (find_courses, plan_timetable). Verb/noun patterns are also mixed, with course_info being a noun while most others are verb_noun.
Ten tools is a reasonable size for a timetable-builder server, covering authentication, discovery, planning, and sharing. The three generic discovery/read/result tools add some surface area that may be infrastructure-heavy relative to the core workflow.
The core lifecycle is well covered: login/status/session cleanup, course search, detailed course info, timetable planning, and sharing. Minor gaps remain around managing or retrieving previously saved timetable states and around degree-explorer capabilities hinted at in the login tool.