F
licenseA
qualityB
maintenanceProvides read-only access to Librus parent account data for multiple children, enabling retrieval of grades, attendance, timetable, calendar, homework, announcements, messages, and attachments via MCP.
11
1
-
librus-mcp
Related Servers
Alternatives to librus-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI apps to read a student's Moodle courses, upcoming and overdue due dates, assignment submission statuses, course grades, gradebook items and announcements. It is strictly read only, so it can never submit, edit or delete anything.11135 npmMIT
- AlicenseAqualityBmaintenanceProvides read-only access to FreeStyle Libre CGM glucose readings via LibreLinkUp, enabling users to list patients, get current glucose with trend, view 12-hour graphs, and retrieve logbook events.436 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables guardians to securely query read-only Vklass data such as children, news, calendar entries, assignments, grades, meals, and notifications through MCP, with per-user BankID and OAuth 2.1 authentication.MIT
- AlicenseAqualityBmaintenanceEnables AI apps to read a student's courses, due dates, grades, missing work, announcements, modules, discussions, syllabus, and calendar events in a read-only way. It cannot submit, edit, or delete anything, and credentials go only to the user's own school.14134 npmMIT
- AlicenseAqualityCmaintenanceEnables read-only access to NYU Brightspace for deadlines, assignments, grades, announcements, and course content.16MIT
TDQS
A3.9/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clear, distinct responsibility: list linked accounts, read a specific API resource, and clear the session. The profiles tool explicitly points to librus_get, removing ambiguity.
Naming Consistency4/5
All tools share the consistent librus_ prefix and snake_case style, making them easy to recognize. There is a minor inconsistency between noun-based librus_profiles and verb-based librus_get/librus_logout.
Tool Count5/5
Three tools is a minimal but well-scoped set for a read-only, session-based Librus API bridge. Each tool serves a real workflow step: discovering accounts, reading data, and ending the session.
Completeness3/5
The session lifecycle is covered, but librus_get is generic and does not enumerate which resources are supported. An agent may struggle to know what API resources can actually be requested.
Maintenance
ActivitySlowing
ResponsivenessNo issues