edookit-mcp
Related Servers
Alternatives to edookit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables parents and students to interact with the Edookit school portal through MCP, including viewing grades, assignments, timetables, attendance, messages, payments, and more, as well as submitting absence excuses and sending messages.211ISC
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to retrieve and work with Moscow Electronic School data, including schedules, homework, grades, rankings, school info, meals, passes, olympiads, and portfolio, via authenticated MCP tools.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to read a family's EduPage school accounts — timetables, grades, homework, tests, absences, messages, attachments and meal menus — across multiple children and schools, plus a few guarded write actions like sending messages and ordering meals. Sessions are captured by signing in once in Chrome and stored only as cookies in the macOS Keychain, so no password is ever kept.85 PyPIGPL 3.0
- AlicenseAqualityCmaintenanceMCP server that connects Claude to Edupage, a school information system used across Europe. Provides access to timetables, grades, homework, messages, students, teachers, and more.251GPL 3.0
- AlicenseAqualityBmaintenanceEnables AI agents to query and manage EduPage school accounts, including timetables, grades, homework, meals, messages, multi-school discovery, role-aware student switching, and 2FA login.31131 PyPI4MIT
- AlicenseAqualityCmaintenanceLets an AI agent read and manage a family's EduPage school data, including timetables, homework, grades, messages, absences, events, and canteen meals, and also send messages to teachers or order meals.161MIT
TDQS
Scored across 46 tools
Many tools are module-prefixed, but several clusters are hard to distinguish: lessons_list, attendance_daily_schedule, direct_attendance_lessons, and changed_timetable all serve timetable-ish purposes. payments_types and payments_categories are nearly indistinguishable from their descriptions, and person_search, student_personal_data, and attendance_students overlap around person data.
Snake_case and module prefixes are reasonably consistent, but verb usage is not: read endpoints appear as bare nouns (attendance_students), list_* (lessons_list), and *_by_date (attendance_passages_by_date). Create operations mix insert_ and create_, and a few tools like person_search and changed_timetable break the module_prefix pattern.
At 46 tools, this is far above the 25-tool threshold and will be difficult for agents to navigate efficiently. The breadth is partly justified by multiple modules, but many tools are trivial version or reference-data endpoints that could be consolidated or removed.
Payments has solid CRUD coverage, and attendance includes reading, inserting, and excuse workflows. However, attendance passages and attendance records are insert/read-only with no update/delete, and lessons, courses, evaluations, and individual goals are mostly read-only or single-purpose, leaving notable lifecycle gaps.