McGill VSB MCP
Related Servers
Alternatives to McGill VSB MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceExposes USC's public course catalog API to AI agents, enabling natural-language queries about courses, GE requirements, schedules, and fees with optional filters for days, times, and open sections.16MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables University of Toronto students to access academic data from ACORN and Quercus via AI assistants. It provides tools to retrieve course schedules, enrollment details, syllabi, assignments, and announcements.-
- FlicenseNot gradedqualityDmaintenanceEnables fetching and analyzing COMSATS University timetables via natural language, bridging Claude Desktop with the live university timetable system.-
- FlicenseAqualityDmaintenanceEnables searching Brown University courses, getting detailed course info, and checking schedule conflicts via natural language, using the university's public course catalog API.5-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to browse your own university courses by downloading files, slides, announcements, deadlines, grades and lecture transcripts to your machine, then answering questions and searching across them through MCP tools. It logs in with your own account and refreshes only what changed.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Desktop to access your McGill University myCourses account, letting you ask about your courses and upcoming deadlines in plain language.Apache 2.0
TDQS
Scored across 4 tools
Each tool occupies a distinct step in the course-planning workflow: search_courses finds courses, get_sections expands them, check_conflicts validates selections, and generate_schedules builds combinations. There is no functional overlap, and the descriptions reinforce the boundaries.
All four names follow a clean snake_case verb_noun pattern (search_courses, get_sections, check_conflicts, generate_schedules). The convention is uniform and immediately readable.
Four tools map neatly onto the search → expand → validate → generate pipeline without redundancy. The scope is tight and each tool earns its place.
The surface covers the full planning lifecycle from discovery through conflict checking to schedule generation, with sensible reuse of section objects across tools. Minor gaps exist (e.g., no explicit term-listing or saved-schedule retrieval), but agents can work around these.