remind-mcp
Related Servers
Alternatives to remind-mcp
No user-submitted related servers found.
Related Servers
- 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.16MIT
- AlicenseAqualityFmaintenanceEnables Claude to access the ParentSquare school-parent communication platform via its web interface and internal APIs, covering parent features like feeds, calendars, messages, forms, and payments, plus school admin roster management such as students, guardians, classes, and staff.48MIT
- AlicenseAqualityAmaintenanceEnables Claude to access ParentSquare school-parent communication platform, including feeds, calendar, conversations, and media files.4846 PyPI14MIT
- AlicenseAqualityCmaintenanceEnables Claude to access school information system data such as timetables, grades, homework, messages, students, teachers, and meal information, including meal ratings.26GPL 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.31383 PyPI3MIT
- AlicenseAqualityBmaintenanceGives MCP-capable agents read-only access to a Google Classroom account, exposing courses, coursework, due dates, announcements, rosters and student submissions as callable tools. Nothing can be created, edited or deleted through it.8MIT
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes (account read, healthcheck, send, settings read/write), and the descriptions explicitly frame remind_list_entities as the entry point while get_classes/list_chats/messages peel off detail. There is mild overlap: remind_list_entities lists both classes and chats that get_classes and list_chats also cover, reminder_graphql can duplicate any typed read, and get_notification_settings returns devices that set_notification_devices mutates, so a few boundaries require reading descriptions to resolve.
Almost all tools follow a consistent remind_verb_noun pattern (remind_get_classes, remind_list_chats, remind_send_message, remind_set_notification_devices, etc.). Three deviate from the verb_noun form: remind_me, remind_healthcheck and remind_graphql, but the shared remind_ prefix keeps the set readable and predictable.
Ten tools is well within the sweet spot for a client API server, and each appears to earn its place: auth/session, account, notifications read/write, entity listing, class detail, chat listing, message read/send, and a read-only GraphQL escape hatch. No redundant or filler tools.
The domain (Remind messaging client) is well covered for its core flow: discover entities, inspect classes/chats, read and send messages, plus a GraphQL hatch for unexposed reads. Gaps are minor: notification settings can only be toggled for devices, not the preference flags, and since mutations are rejected by the GraphQL tool there is no write path for class/chat administration or message-level actions.