canvas-teacher-mcp
Related Servers
Alternatives to canvas-teacher-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA teacher-facing MCP server that wraps the Canvas LMS REST API, enabling AI assistants to create and manage course content across multiple Canvas courses.3 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server for Canvas LMS that exposes courses, assignments, modules, pages, files, grades, and submissions as tools for AI agents.-
- AlicenseAqualityBmaintenanceMCP server that connects AI assistants to Instructure Canvas LMS, enabling teachers and administrators to manage courses, assignments, grades, and more through natural language.8021 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.3 npmMIT
- 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.111 npmMIT
TDQS
Scored across 58 tools
While many tools have clear distinct purposes, there are several clusters with overlapping responsibilities, such as the grading skills (grade, grade-git-program, grade-nb), page builders (assignment-page-builder, git-asmt-page, build_coding_assignment_page), and document formatters (gws-doc, gws-richdoc, gslides-format). Descriptions help differentiate them, but an agent could still mis-select in these areas.
Tool names mix snake_case (list_courses, get_page) with kebab-case (agenda-wrapup, assignment-page-builder) and even a verb-less noun style (git-asmt-repo, quiz-builder). Verb prefixes are inconsistent (read vs get vs list, create vs build vs add), making the naming pattern unpredictable.
With 58 tools, the server far exceeds the typical well-scoped range of 3-15 and even the 25+ threshold for excessive. The large number likely reflects an integrated suite of skills and utilities, but it risks overwhelming agents and increasing selection errors.
The tool surface covers a comprehensive teaching workflow: assignments, quizzes, pages, modules, announcements, submissions, grading, and Google Docs. Minor gaps exist, such as no delete operations for most resources and no list/get for announcements, but the core lifecycle is well represented.