Canvas MCP
Related Servers
Alternatives to Canvas MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA remote MCP server for querying Canvas LMS courses, assignments, and grades. Enables natural language interaction with Canvas data via MCP clients like Claude Desktop.11 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server for Canvas LMS that exposes courses, assignments, modules, pages, files, grades, and submissions as tools for AI agents.-
- AlicenseNot gradedqualityBmaintenanceA local MCP server that exposes Canvas LMS courses, assignments, grading, discussions, modules, pages, files, messaging, and peer reviews to an AI assistant through about 100 Markdown-returning tools, with preview-then-confirm behavior for any write operations.MIT
- 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.3021 npm2MIT
- AlicenseNot gradedqualityCmaintenanceMCP 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.2MIT
- AlicenseBqualityDmaintenanceA read-only MCP server for Canvas LMS that exposes a user's courses, upcoming work, and assignments as callable tools.3MIT
TDQS
Scored across 12 tools
Each tool maps to a distinct Canvas resource (courses, assignments, grades, modules, announcements, discussions, calendar, todo, quizzes), but the assignment-related cluster (get_assignments, get_upcoming_assignments, get_todo_items, get_submission_status) has partial overlap that relies on descriptions to separate. The descriptions do a good job of clarifying scope (course-scoped vs cross-course vs action-needed vs status check), so misselection is unlikely but not impossible.
Eleven of twelve tools use a clean get_<resource> pattern, which is highly predictable. The single list_courses breaks the pattern slightly, but it is idiomatic and readable.
Twelve tools is squarely in the well-scoped range for a Canvas LMS surface. Each tool covers a distinct data type an agent would plausibly need, with no filler or redundant entries.
The surface is entirely read-only: there is no way to submit an assignment, post to a discussion, mark a todo complete, or fetch course files/pages/module items, which are core Canvas workflows. Reading grades, assignments, and announcements is covered, but the absence of any write operation and of content retrieval (files, pages, single-assignment detail) leaves notable gaps that will cause agent dead ends.