Canvas LMS MCP Server
Related Servers
Alternatives to Canvas LMS MCP Server
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityDmaintenanceEnables managing Canvas LMS courses, assignments, grades, modules, and more from MCP-compatible clients like Claude Desktop, Kiro, or Amazon Q Developer.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to access Canvas LMS academic data such as courses, assignments, grades, and events via MCP tools.-
- AlicenseAqualityBmaintenanceMCP server that connects AI assistants to Instructure Canvas LMS, enabling teachers and administrators to manage courses, assignments, grades, and more through natural language.8013 npm1MIT
- 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.3,780 npmMIT
TDQS
Scored across 163 tools
With 163 tools, several clusters are nearly indistinguishable at first glance: list_enrollments vs list_course_enrollments, get_upcoming_events vs get_my_upcoming_assignments vs list_calendar_events, and the multiple 'needing attention' triage tools. The duplicate view_account_notifications/view_course_structure tools also muddy boundaries. Detailed descriptions help, but misselection risk is high.
The dominant verb_noun convention (list_*, get_*, create_*, update_*, delete_*) is clear and predictable. However, there are notable exceptions like project_grade, next_appointment, health_check, view_* duplicates, and inconsistent list_/get_ usage for gradebook history (list_gradebook_history_days vs get_gradebook_history_day).
163 tools is an extreme count for any MCP server. Even with Canvas's broad API surface, this creates an unwieldy working set full of niche analytics, audit, and accommodation tools that bloat the namespace. A curated core of 20-40 tools would serve agents far better.
Coverage is broad but uneven: courses, assignments, pages, discussions, files, and quizzes have substantial CRUD, yet obvious operations are missing or absent — no delete_calendar_event, no create_quiz despite a reference to it, no update/delete for assignment overrides, no delete for module items, and no conversation read/mark actions. Agents will hit dead ends across several subdomains.