eclass-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ECLASS_URL | No | Base URL of your eClass instance, for example https://eclass.upatras.gr. Used when connecting to a university other than the default University of Thessaly eClass. | |
| ECLASS_PASSWORD | No | Your eClass password. Can be omitted if credentials were stored via the system keyring using `uv run eclass-mcp login`. | |
| ECLASS_USERNAME | No | Your eClass username. Can be omitted if credentials were stored via the system keyring using `uv run eclass-mcp login`. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Read access to a student's Open eClass account (courses, announcements, deadlines, assignments, exercises, documents, messages).
Course codes are the segment after /courses/ in eClass URLs (for example DS101); call list_courses first to find them. Dates are returned both as eClass prints them and normalized in *_iso fields (local time, YYYY-MM-DD HH:MM).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Check that the login works and see which account and eClass site are in use. |
| list_coursesA | List the courses the student is enrolled in, with code, title and teachers. |
| get_course_toolsC | Which modules (documents, assignments, exercises, forum...) a course has enabled. |
| get_announcementsA | Latest announcements across all courses, or for one course if a code is given. Bodies are plain text; use get_announcement for the full text of one. |
| get_announcementC | Full text of one announcement. |
| get_deadlinesA | Upcoming calendar events for all courses: assignment and exercise deadlines,
agenda entries, teleconferences and personal events. Looks |
| get_assignmentsC | Assignments of a course with deadline, submission status and grade. |
| get_assignmentB | Details of one assignment: description, attached files, deadline, and the student's own submission if there is one. |
| get_exercisesB | Exercises (quizzes) of a course with their availability window and whether the student has attempted them. |
| list_documentsB | Files and folders in a course's Documents area. Pass a folder's |
| download_documentA | Download a document (or a whole folder as a zip) by its |
| get_messagesC | Personal and course messages. |
| get_messageB | Full text of one message, with sender, recipients and attachment if any. |
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 13 tools
Each tool maps to a distinct resource or action, and the plural/singular pairs (get_announcements vs get_announcement, get_assignments vs get_assignment, get_messages vs get_message) are explicitly cross-referenced in descriptions to steer selection. Minor overlap remains between get_deadlines and get_assignments (both surface assignment deadlines), but the framing as calendar vs. course context keeps them separable.
Nearly all tools follow a snake_case verb_noun pattern (list_courses, get_assignment, download_document). Deviations are minor: 'whoami' breaks the pattern entirely, and the set mixes 'list_' and 'get_' for resource enumeration in ways that are not strictly principled (list_documents but get_assignments).
Thirteen tools is squarely in the sweet spot for an LMS client and each one covers a distinct area (auth, courses, deadlines, assignments, exercises, documents, messages). No tool appears redundant or filler.
The surface is entirely read-only: a student can inspect assignments and submissions but cannot submit, upload, or post anything, and get_course_tools advertises forum modules that have no corresponding read tool. Announcements, assignments, exercises, documents and messages are covered, but the lifecycle stops at viewing, leaving notable dead ends for a student-facing client.