F
licenseNot graded
qualityD
maintenanceEnables AI assistants to automatically pull Canvas LMS course materials into Obsidian, syncing files, assignments, grades, and announcements organized by course and module.
-
mcp-canvas-utem
by k0ngan
Related Servers
Alternatives to mcp-canvas-utem
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP-compatible assistants to read Canvas course information—including courses, assignments, syllabi, modules, pages, and announcements—through a local read-only server.10MIT
- AlicenseBqualityAmaintenanceA local server that enables interaction with Canvas Learning Management System API through Claude Desktop, allowing users to manage courses, access assignments, view announcements, and retrieve course materials.115714 PyPI320MIT
- 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
- AlicenseBqualityBmaintenanceStudent-focused Canvas LMS MCP server with 209 tools: what-if grades, the score you need on the final, deadlines and missing work across every course, submissions with confirm-before-send, discussions and inbox. Runs locally with npx, nothing exposed to the internet.6237856 npm2MIT
TDQS
B3.2/5.0
Scored across 12 tools
Disambiguation3/5
There is real overlap: canvas_sync_course is effectively a superset of canvas_list_course_assignments, canvas_course_updates, canvas_download_course_files, and canvas_course_inventory, so an agent must infer whether to run the full sync or the incremental partial tools. Descriptions do clarify the distinction (partial notes vs full sync, no-write vs write), which keeps it from being worse, but the boundaries are fuzzy.
Naming Consistency4/5
All tools share the canvas_ prefix and snake_case, and most follow verb_noun (list_courses, sync_course, download_pdf). A few deviate into noun phrasing (canvas_course_inventory, canvas_course_updates, canvas_vault_status), which is a minor inconsistency but still readable.
Tool Count4/5
Twelve tools is a well-scoped size for a Canvas-to-vault integration. A few partial-list tools feel like they could be folded into the sync tools, so it is slightly heavy rather than perfectly lean.
Completeness4/5
Coverage is strong for the sync-to-vault purpose: connection check, course/assignment/task listing, inventory, updates, full sync, downloads, raw source export, and vault status. Minor gaps exist around per-assignment detail or submission/grading views, but core lifecycle is covered.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues