google-classroom-mcp
Related Servers
Alternatives to google-classroom-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to read Google Classroom data—including coursework, submissions, announcements, and Drive attachments—through a remote, OAuth-protected MCP server with interactive Google sign-in.-
- AlicenseAqualityBmaintenanceEnables MCP clients to interact with Google Classroom, providing tools to manage courses, coursework, submissions, announcements, materials, and rosters, including actions like turning in and reclaiming assignments.12MIT
- FlicenseNot gradedqualityCmaintenanceIntegrates Google Classroom with LLMs and AI agents via MCP. Enables listing courses, assignments, announcements, and generating prioritized TODO summaries.1-
- AlicenseAqualityBmaintenanceEnables students to query Google Classroom courses, pending assignments, grades, announcements, and materials, and to attach files or submit assignments, with support for multiple Google accounts from any MCP client.9MIT
- FlicenseAqualityCmaintenanceEnables Claude to read and write Google Classroom data, including courses, coursework, materials, announcements, rosters, submissions, and Drive attachment contents.15-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to operate Google Classroom, letting users list courses and students, check assignment submissions, and create coursework and announcements through natural language.-
TDQS
Scored across 8 tools
Each tool targets a distinct resource and scope: courses, single course, coursework, due-soon across courses, announcements, teachers, students, and submissions. The only near-overlap is list_coursework vs list_due_soon, but the descriptions clearly distinguish per-course listing from cross-course due-date aggregation.
Consistent snake_case verb_noun pattern throughout (list_courses, get_course, list_coursework, etc.). The single 'get_course' appropriately pairs with 'list_courses' for singular retrieval, so the convention is predictable.
Eight tools is well-scoped for a read-oriented Classroom client. Each tool earns its place by covering a distinct entity or query, with no redundancy or filler.
Read coverage is solid (courses, coursework, submissions, announcements, rosters), but the surface is entirely read-only. Common Classroom mutations—creating courses/coursework, submitting assignments, grading, posting announcements, or updating/deleting—are absent, creating dead ends for write-oriented workflows.