parentsquare-mcp
Related Servers
Alternatives to parentsquare-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables Claude to access ParentSquare school-parent communication platform, including feeds, calendar, conversations, and media files.488MIT
- FlicenseAqualityCmaintenanceMCP server that gives Claude read access to your ParentSquare parent account, enabling queries about school posts, calendars, messages, directory, signups, forms, payments, and files. It also parses image/PDF attachments so calendar flyers are accessible.23-
- FlicenseAqualityCmaintenanceEnables Claude to read and write Google Classroom data, including courses, coursework, materials, announcements, rosters, submissions, and Drive attachment contents.15-
- AlicenseBqualityCmaintenanceEnables Claude to interact with Canvas LMS, allowing natural language queries about courses, deadlines, grades, and feedback.29MIT
- FlicenseAqualityDmaintenanceEnables natural language queries about grades, GPA, attendance, and schedules by connecting Claude to StudentVue school dashboards. Includes analytical tools for grade simulation, what-if scenarios, and academic performance tracking based on live school data.19-
- FlicenseAqualityCmaintenanceA local MCP server for reading ParentSquare data (feeds, calendar, messages, directory, groups, and more) using undocumented internal APIs. It enables Claude, Cursor, and other MCP clients to access your ParentSquare account via stdio.231-
TDQS
Scored across 48 tools
Most tools are clearly scoped to distinct resources (students, staff, classes, parents, feeds, payments), and the descriptions reinforce boundaries. Minor overlap exists between list_students/get_student and list_staff/get_staff_member, and between list_class_students and get_class, but the descriptions clarify the differences.
The set overwhelmingly follows a consistent verb_noun pattern (list_*, get_*, add_*, edit_*, remove_*, move_*, set_*, submit_*, download_*, invite_*, bulk_invite_*). Minor deviations: get_feeds/get_post vs list_* for other read operations, and get_student_dashboard doesn't follow the resource pattern, but these are understandable.
48 tools is on the heavy side, but the server covers a broad domain (school communication, rosters, classes, staff, parents, payments, forms, photos, calendar). The count is justified by the breadth, though it pushes the upper bound of what an agent can comfortably navigate.
The surface covers the core ParentSquare domains well: read operations for feeds, conversations, calendar, photos, files, directory, groups, signups, notices, polls, payments, forms, volunteer hours, and full admin CRUD for students, parents, staff, and classes. Minor gaps: no way to create posts, send messages, or unlink guardians, and no delete operations for students/staff/classes, but the stated scope (school info + roster management) is largely complete.