F
licenseNot graded
qualityC
maintenanceRemote 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.
-
fuxam-student-mcp
Related Servers
Alternatives to fuxam-student-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server for the University of Vienna's course catalogue (u:find), enabling natural language queries for courses, programmes, staff, and schedules. Read-only, no account or API key required.13MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying academic data from Universitat Jaume I, including subjects, degrees, locations, and schedules, via MCP-compatible clients.MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying academic data such as subjects, degrees, locations, and schedules from Universitat Jaume I via MCP tools.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for querying student information, validating result data, and analyzing student results from a local database.-
- FlicenseNot gradedqualityBmaintenanceMCP server exposing a university course catalog with tools for searching courses, looking up prerequisites and instructors, and generating prerequisite graphs, plus resources and a prompt template for AI academic advisors.-
TDQS
A3.7/5.0
Scored across 21 tools
Disambiguation5/5
Each tool has a clearly distinct purpose, ranging from search and listing to booking and waitlist management. Overlaps like list_enrolled_courses vs list_bookable_courses are differentiated by their scope (enrolled vs bookable), and get_learning_unit_details vs get_module_details target different entities.
Naming Consistency4/5
Most tools follow a verb_noun pattern (list_*, get_*, book_*, unbook_*, join_*, leave_*). Minor inconsistencies exist, such as 'search_fuxam' and 'explore_learning_options' not using the same prefix structure, but the overall naming is coherent and readable.
Tool Count4/5
With 21 tools, the set is fairly large but justified by the breadth of student operations: reading data, booking, waitlists, conflict checking, and scheduling. The count is on the higher end but still within a reasonable range for a comprehensive student management server.
Completeness4/5
The tool surface covers core student actions: search, list, view details, book/unbook, join/leave waitlists, check conflicts, and access appointments, deadlines, exams, todos, and pinned courses. Minor gaps like a dedicated 'get_student_info' or update operation exist, but the core domain is well represented.
Maintenance
ActivityMaintained
ResponsivenessSyncing