learnJCU MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEARNJCU_ACCOUNT | No | The saved account to use, instead of being asked. Same as `--account`. | |
| LEARNJCU_BROWSER | No | The browser for sign-in, as a path to its executable or a channel (`msedge`, `chrome`). Defaults to your system default browser. If that is Firefox or Safari, which can't be automated, an installed Edge or Chrome is used instead. | |
| LEARNJCU_MCP_HOME | No | The session folder. Defaults to `~/.learnjcu-mcp`. | ~/.learnjcu-mcp |
| LEARNJCU_DOWNLOAD_DIR | No | The download folder. Defaults to `~/Downloads/learnjcu`. | ~/Downloads/learnjcu |
| LEARNJCU_NO_AUTO_LOGIN | No | Set to `1` to stop the CLI and the MCP server from refreshing an expired session by themselves. | |
| LEARNJCU_NO_UPDATE_CHECK | No | Set to `1` to stop the MCP server from checking GitHub for a newer version when it starts. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| learnjcu_list_accountsA | List the saved University accounts (each has its own sign-in) and which one is chosen for this session. Use when the user asks which accounts are saved, or before asking them which account to use. |
| learnjcu_select_accountA | Choose which saved account the other tools use for the rest of this session. Call it after the user has said which account they mean; never pick one for them. |
| learnjcu_statusA | Check whether a LearnJCU session is saved and when it expires. With several saved accounts and none chosen, it lists them all. |
| mystudent_statusA | Check whether a MyStudent session is saved and when it expires. With several saved accounts and none chosen, it lists them all. |
| studentfirst_statusB | Check whether a StudentFirst session is saved. With several saved accounts and none chosen, it lists them all. |
| learnjcu_loginA | Sign in to LearnJCU or refresh an expired session. Call this whenever a LearnJCU tool says the session expired or you are not signed in. Each saved account has its own sign-in; with several, pass account (the user is asked when you leave it out). It first refreshes silently (a few seconds, no window). If the user has to sign in, it opens the sign-in page in their default browser: tell the user a browser window opened and ask them to sign in there. If the result says waitingForUser, call again after the user says they are done. Never ask the user for their password; they type it in the browser. |
| mystudent_loginA | Sign in to MyStudent or refresh an expired session. Call this whenever a MyStudent tool says the session expired or you are not signed in. MyStudent uses the same JCU single sign-on as LearnJCU, so this is usually silent. Each saved account has its own sign-in; with several, pass account (the user is asked when you leave it out). Accounts are created by learnjcu_login; sign in to LearnJCU first if none is saved. It first refreshes silently (a few seconds, no window). If the user has to sign in, it opens the sign-in page in their default browser: tell the user a browser window opened and ask them to sign in there. If the result says waitingForUser, call again after the user says they are done. Never ask the user for their password; they type it in the browser. |
| studentfirst_loginA | Sign in to StudentFirst or refresh an expired session. Call this whenever a StudentFirst tool says the session expired or you are not signed in. StudentFirst (JCU Singapore) has its own user name and password, not the JCU single sign-on. When a window opens, ask the user to sign in there and to let the browser save the password, so later refreshes need nothing from them. Each saved account has its own sign-in; with several, pass account (the user is asked when you leave it out). Accounts are created by learnjcu_login; sign in to LearnJCU first if none is saved. It first refreshes silently (a few seconds, no window). If the user has to sign in, it opens the sign-in page in their default browser: tell the user a browser window opened and ask them to sign in there. If the result says waitingForUser, call again after the user says they are done. Never ask the user for their password; they type it in the browser. |
| learnjcu_whoamiB | Show the signed-in LearnJCU user. |
| learnjcu_list_coursesA | List the modules/courses you are enrolled in on LearnJCU, most recently accessed first. Use when the user asks about their courses or modules, or you need a course id for another LearnJCU tool. |
| learnjcu_list_announcementsA | List recent announcements for a course, newest first. |
| learnjcu_list_contentsA | List items in a course outline. Omit contentId for the top level; pass a folder/learning module id to list its children. Use when the user asks what is in a course, or to find an assignment or other item in it. |
| learnjcu_get_contentA | Get one content item with its full text and the list of its files, including files embedded in the page (ids like "embedded-0"). Use when the user asks for the details of an assignment or other item: its brief, instructions and attached files. |
| learnjcu_download_attachmentA | Download a file from a content item (an attachment id, or an "embedded-N" id from learnjcu_get_content) into the local Downloads/learnjcu folder and return its path. |
| learnjcu_my_gradesA | Show the gradebook for a course: each assessment with due date, your submission status, grade and feedback. Use when the user asks about a course's assignments, their grades or feedback. |
| learnjcu_upcoming_deadlinesA | Scan all current courses for gradebook items due in the next N days (default 14), with your submission status. |
| learnjcu_calendarB | List LearnJCU calendar items (course events, due dates, personal events) between two dates. Default: next 4 weeks. |
| mystudent_overviewA | Show the MyStudent dashboard (JCU's student administration portal): your contact details, study plan, class registrations, outstanding payments, tasks to complete, today's calendar, and forms in progress or available. Use when the user asks about their enrolment, fees, tasks or forms in MyStudent, or their student record. |
| mystudent_study_planA | Show your course in MyStudent and every subject in its structure with its status: enrolled (and in which study period), completed, exempt or credited, or planned for a later period, plus advanced standing. Takes about 10 seconds (the page is rendered in a hidden browser). Use when the user asks about their degree progress, which subjects are left, or what they are enrolled in. |
| mystudent_pageA | Read one MyStudent page in full, in a hidden browser (about 10 s, plus 3-5 s for each section). Pages: details (personal details, contacts and addresses, educational background, sanctions, communications, forms); study (course structure, course overview, self-service reports on offer, withdrawal: census and last-withdrawal dates per subject); class_registrations; finances (summary, outstanding transactions and amounts payable, payment receipts, forms, payment preferences); tasks (enrolment tasks still to do); calendar (this week); forms (forms you can fill out); form_responses (your draft and submitted forms); applications (course applications and offers). Sections: details (summary, contacts, education, sanctions, communication, forms); study (course, overview, reports, withdrawal); class_registrations; finances (summary, transactions, receipts, forms, preferences); tasks; calendar; forms; form_responses; applications. Pass section to read only one (faster). This only reads: it never saves, requests, pays, enrols, withdraws or submits anything; tell the user to do those on the MyStudent website. Use when the user asks for something in MyStudent that mystudent_overview does not show in full. |
| studentfirst_overviewA | Show StudentFirst (JCU Singapore): classes in the next 8 days with time and room, overall class and campus attendance against the 90% minimum, and each class with how many sessions were attended. Use when the user asks about their timetable, next classes, rooms or attendance at JCU Singapore. |
| studentfirst_class_attendanceA | List every session of your StudentFirst classes with date, time, room and whether attendance was recorded as present, absent or not yet recorded. Use when the user asks which classes they missed or the attendance of one subject. |
| studentfirst_leave_applicationsA | List your StudentFirst leave applications with dates and status. Use when the user asks about leave they applied for. This tool does not apply for leave; the user does that on the StudentFirst website. |
| studentfirst_noticesA | Show the StudentFirst notices, such as updates to the JCU Singapore student contract and public holidays. |
| learnjcu_list_submissionsA | Show a LearnJCU assignment's submission settings (due date, attempts allowed, file/text allowed) and every attempt you have made, newest first, with status, receipt and files. Use when the user asks for an assignment's details (due date, attempts left, what can be submitted) or what they have already submitted, and before submitting. |
| learnjcu_api_getA | Read-only escape hatch: GET any Blackboard Learn public REST endpoint under /learn/api/public/. |
| learnjcu_check_updateA | Check whether a newer version of learnjcu-mcp is on GitHub, and list what it adds. Use when the user asks about updates or what is new. |
| learnjcu_updateA | Update this copy of learnjcu-mcp to the latest version from GitHub (git fetch, switch to main and fast-forward, npm install). Only use after the user has said yes to updating. Always call with dryRun: true first, show the plan, then call with confirm: true. The user must restart the MCP client afterwards. |
| learnjcu_submitA | Submit files (and optional text) to a LearnJCU Ultra assignment as a new attempt. Course staff see it at once, and it may count as your graded attempt. Use when the user asks to submit an assignment on LearnJCU. If the item links to an external tool, submit there instead. Always call with dryRun: true first, show the plan, and wait for the user to confirm. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.