cmu-soc
Related Servers
Alternatives to cmu-soc
No user-submitted related servers found.
Related Servers
- 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.-
- AlicenseAqualityBmaintenanceGives 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.423 npm2MIT
- AlicenseAqualityBmaintenanceEnables Claude and ChatGPT to help users pick UC Irvine classes by searching live course sections, comparing grade distributions by instructor, checking prerequisites and AP credit, and detecting schedule conflicts, all through tools, guided prompts, and reference resources.16AGPL 3.0
- AlicenseAqualityDmaintenanceEnables searching and retrieving course details, schedules, prerequisites, and instructor information from the CMU course catalog via the ScottyLabs API.92MIT
- FlicenseNot gradedqualityDmaintenanceEnables fetching and analyzing COMSATS University timetables via natural language, bridging Claude Desktop with the live university timetable system.-
- 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-
TDQS
Scored across 9 tools
Most tools have crisp, distinct scopes (semesters, departments, buildings, exams, walk time), and descriptions explicitly redirect between related tools (search_courses → get_course_details). The one soft spot is the trio get_course_details / get_course_info / get_course_description, where 'info' vs 'description' vs 'details' cover overlapping metadata (description, prereqs, coreqs) and rely on subtle distinctions like catalog-year vs offered-course coverage to be told apart.
Every name follows a clean verb_noun snake_case pattern: list_buildings, list_semesters, list_departments, search_courses, get_course_details, get_final_exams, estimate_walk_time. Verbs are used consistently by intent (list = reference data, get = single-entity detail, search = query), with no camelCase or style drift.
Nine tools sit comfortably in the well-scoped 3-15 range, and each maps to a concrete step in the workflow: resolve semester/department → search courses → drill into sections/info/catalog → check finals. The walk-time pair (estimate_walk_time + list_buildings) is a justified adjunct that its companion tool supports directly.
The surface covers the full course-research lifecycle: semesters, departments, course search, section times, catalog prereqs, and final exams, with explicit notes that seats and rooms are not public and therefore not gaps. The main missing operation is a cross-department or title-based course search — search_courses is department-scoped — plus no lookup for cross-listed course equivalence beyond what get_course_info returns.