librus-mcp
Related Servers
Alternatives to librus-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceProvides 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.111-
- AlicenseNot gradedqualityCmaintenanceProvides 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.MIT
- 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
- AlicenseAqualityCmaintenanceEnables read-only access to NYU Brightspace for deadlines, assignments, grades, announcements, and course content.16MIT
- AlicenseAqualityCmaintenanceEnables reading study data and downloading documents from HISinOne campus portals using the signed-in account.91MIT
- AlicenseBqualityAmaintenanceEnables Claude to query your KRÉTA student data locally and read-only, including timetables, homework, grades, tests, and absences, using your own credentials via OAuth/PKCE.203Apache 2.0
TDQS
Scored across 3 tools
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.
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.
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.
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.