canvas-parent-mcp
Related Servers
Alternatives to canvas-parent-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Canvas LMS with automatic OAuth authentication. Enables interaction with courses, assignments, grades, modules, discussions, quizzes, files, calendar, messaging, and more without manual API token management.243 npmMIT
- FlicenseAqualityCmaintenanceEnables MCP-compatible clients to read courses, assignments, announcements, files, and grades from a Canvas LMS instance.10-
- AlicenseAqualityAmaintenanceRead-only MCP server for Canvas LMS that works without API tokens by using session cookies, enabling AI assistants to access courses, assignments, grades, announcements, and more.3023 npm2MIT
- AlicenseAqualityAmaintenanceRead-only MCP server for Canvas LMS that exposes tools to list courses, assignments, grades, submissions, syllabi, announcements, modules, pages, and files, without any write operations.1113 npm1MIT
- AlicenseBqualityCmaintenanceA read-only MCP server for Canvas LMS that exposes a user's courses, upcoming work, and assignments as callable tools.3MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server for Canvas LMS that enables querying courses, assignments, grades, modules, and more from any MCP-compatible AI client.8 npmMIT
TDQS
Scored across 19 tools
Most tools map to distinct Canvas resources (files, discussions, courses, assignments, submissions, conversations, announcements). However, canvas_list_calendar_events, canvas_list_upcoming_events, and canvas_list_planner_items overlap meaningfully in what they return, which could mislead an agent.
The canvas_ verb_noun pattern is consistent across nearly every tool (list_*, get_*, download_*). Only canvas_healthcheck breaks the verb_noun convention, as it uses a noun instead of an action-object pair.
Nineteen tools is on the heavier side but reasonable for a Canvas integration covering courses, assignments, submissions, files, discussions, conversations, calendar, and planner data. Each tool addresses a distinct resource or workflow, so the count feels slightly large rather than bloated.
The read-only surface is quite comprehensive for a parent/observer use case: courses, grades, missing submissions, assignments, files, discussions, announcements, conversations, calendar, and planner items are all covered. Minor gaps exist (e.g., modules, pages, or quiz-specific endpoints), but agents can handle the main monitoring workflows without dead ends.