edupage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EDUPAGE_PASSWORD | Yes | Your EduPage password | |
| EDUPAGE_TIMEZONE | No | IANA timezone that 'today' is judged in | Europe/Bratislava |
| EDUPAGE_USERNAME | Yes | The username you sign in to EduPage with (usually an email) | |
| EDUPAGE_READ_ONLY | No | Set to 'true' to hide send_message and order_meal tools (read-only mode) | false |
| EDUPAGE_SUBDOMAINS | No | Comma-separated schools, e.g. myschool,otherschool for myschool.edupage.org. If not set, schools are discovered automatically. | |
| EDUPAGE_SESSION_FILE | No | Keep sessions in this file (mode 600) so a two-factor login survives restarts | |
| EDUPAGE_REQUEST_TIMEOUT | No | Seconds to wait for EduPage | 20 |
| EDUPAGE_SESSION_TTL_MINUTES | No | How old a session may get before it is refreshed | 20 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountA | Who is on this EduPage login: the account type (parent or student), every school it reaches (subdomain, school year, email) and every student with their class and school. Call this first to learn the names to pass as |
| get_briefingA | One-call overview for every student (or just |
| get_timetableA | A student's lessons for |
| get_homeworkA | Homework and announced exams (tests, quizzes, oral exams) due between |
| get_messagesA | Messages from teachers and the school (and chats) since |
| get_notificationsA | Everything on the student's EduPage timeline since |
| get_gradesA | A student's marks for the current term, newest first, with a per-subject summary (count and weighted average). Marks run 1 (best) to 5; points and percentage marks include |
| get_absencesA | Absences recorded for a student since |
| get_eventsA | School calendar events for a student between |
| get_substitutionsA | The school's substitution plan for |
| get_mealsA | The school canteen menu for |
| get_school_infoA | Facts about a school (by subdomain or a student's name): the bell schedule with each period's start and end, the school's email, each student's class with its class teachers and home classroom, and how many teachers, classes, subjects and rooms it has. |
| list_teachersA | Teachers at a school (by subdomain or a student's name), optionally filtered by |
| send_messageA | Send a new EduPage message from this account to one or more teachers at a school (by subdomain or a student's name). |
| order_mealA | Choose a menu for a student's canteen meal on |
| complete_loginA | Finish an EduPage login that asked for a second factor. After the user approves the login in the EduPage app, call this with no |
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 16 tools
Every tool targets a distinct EduPage resource or action, and the descriptions clearly separate overlapping areas like get_messages vs. get_notifications and get_timetable vs. get_substitutions. An agent should be able to select the right tool without confusion.
Tool names almost universally follow a snake_case verb_noun pattern, with get_* for reads and imperative verbs like send_, order_, and complete_ for actions. list_teachers is a conventional collection-naming exception rather than an inconsistency.
At 16 tools, the surface is just above the ideal 3-15 range, but the EduPage domain is genuinely broad and each tool covers a meaningful module. The count feels comprehensive rather than bloated.
The set covers nearly every core student/parent workflow: timetable, homework, messages, grades, absences, meals, events, substitutions, school info, and login. A few smaller capabilities are missing, such as toggling homework completion or detailed payment actions, but the main workflows have no dead ends.