Skip to main content
Glama
SleepyPandas

UofT Timetable Builder MCP

by SleepyPandas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to UofT Timetable Builder MCP

No user-submitted related servers found.

    Related Servers

    • ScarletPlan

      heetshah15
      F
      license
      A
      quality
      D
      maintenance
      Local-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
      -

    • ucla-soc-mcp

      aaditsingh07
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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.
      -

    • cmucourses-connector

      SamEthanMathew
      F
      license
      Not graded
      quality
      C
      maintenance
      Remote 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.
      -

    • LettuceMeet MCP

      brchn6
      F
      license
      Not graded
      quality
      B
      maintenance
      Unofficial MCP tools for LettuceMeet to create polls, view responses, and find meeting overlaps via CLI or MCP server.
      -

    • crewmeister-api

      BelStark
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to interact with the Crewmeister API over local stdio, covering operations for members, teams, time tracking, salary exports, and related platform resources.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Tools are mostly distinct: authentication flow (login, auth_status, forget_session), discovery (discover), read operations (read, result), and saving (save_timetable). Minor overlap between 'read' and 'result' as both handle retrieval, but result is specifically for snapshot paging, so it's acceptable.

    Naming Consistency3/5

    Most tools follow a 'uoft_' prefix with verb or noun, but 'save_timetable' breaks the pattern. Verbs are inconsistent (login, discover, read, forget_session) vs nouns (auth_status, result). Still readable, but not a uniform convention.

    Tool Count5/5

    7 tools is well within the ideal 3-15 range. Each tool serves a clear purpose: authentication management, discovery, reading, result handling, and saving. No redundancy or bloat.

    Completeness3/5

    The set covers authentication, discovery, reading, and saving timetable states, but lacks explicit tools for creating or modifying timetables (only saves a provided state). This may require agents to construct states themselves, a notable gap for a 'Timetable Builder' server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources