learnJCU MCP
Related Servers
Alternatives to learnJCU MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables read-only access to Blackboard Ultra course announcements, deadlines, grades, and materials, allowing users to download study materials and save summaries through an MCP interface.17MIT
- AlicenseAqualityBmaintenanceGives Claude, Codex, Cursor and any other MCP client read access to your courses, content, files, grades, deadlines, announcements and discussions, using your own browser session.3116 npm5MIT
- AlicenseAqualityBmaintenanceEnables MCP-capable AI clients to read USTC Blackboard courses, assignments, announcements, and courseware, and to submit standard file assignments through a preview-then-confirm workflow using per-user local credentials.9MIT
- FlicenseAqualityBmaintenanceEnables students to access Moorle courses, assignments, grades, announcements, and notifications through authenticated MCP tools.11-
- AlicenseNot gradedqualityBmaintenanceEnables users to retrieve Modeus schedules, iStudent grade/rating data, and eLearn course listings, content, and files through local MCP tools while using their university service login.1Apache 2.0
- AlicenseAqualityBmaintenanceEnables read-only access to University of Leeds Minerva (Blackboard Learn Ultra) and Gradescope through a browser-authenticated session. Supports listing courses, announcements, contents, grades, deadlines and calendar events, downloading attachments, and querying Gradescope assignments and submissions.36ISC
TDQS
Scored across 29 tools
The triple-prefix scheme (learnjcu_/mystudent_/studentfirst_) cleanly separates the three portals, and within each portal most tools target a distinct resource or action. A few boundaries blur: learnjcu_my_grades, learnjcu_list_submissions and learnjcu_upcoming_deadlines all surface due dates plus submission status, and mystudent_study_plan overlaps mystudent_page with section=study. The descriptions do mitigate this (e.g. mystudent_page is explicitly framed as the fallback for what overview doesn't show), so an agent can still choose correctly.
Almost everything follows a predictable snake_case pattern of portal + verb + noun (learnjcu_list_courses, learnjcu_get_content, studentfirst_class_attendance). Minor deviations exist: noun-only names like learnjcu_status, learnjcu_calendar, mystudent_overview, and the bare mystudent_page, plus the possessive learnjcu_my_grades. These are readable and group logically, but the pattern isn't exactly uniform.
29 tools is heavy for a single MCP server, though the count is explained by covering three separate university systems plus auth and self-update tooling. Most tools earn their place, but there is some redundancy (three MyStudent readers, paired check_update/update, paired grades/submissions/deadlines). It sits at the upper edge of what an agent can scan without losing track.
The surface covers the full lifecycle for its stated purpose: per-account auth for all three portals, course/content/attachment access, gradebook and deadlines, submission inspection plus actual assignment submission, and broad read coverage of MyStudent and StudentFirst. Remaining gaps are largely deliberate (MyStudent and StudentFirst are read-only; leave applications, payments and enrolment are explicitly deferred to the websites), which can produce dead ends but not silent failures. Minor gaps like no announcement detail view or discussion tools are workable around.