canvas-api-mcp
Related Servers
Alternatives to canvas-api-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceA read-only MCP server for Canvas LMS that exposes a user's courses, upcoming work, and assignments as callable tools.3MIT
- AlicenseCqualityBmaintenanceAn MCP server for Canvas LMS that enables assistants to read course content, create assignments and pages, set due dates, and post announcements via the Canvas REST API.581MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for Canvas LMS that exposes courses, assignments, modules, pages, files, grades, and submissions as tools for AI agents.-
- 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
- AlicenseBqualityAmaintenanceMCP server for Canvas LMS, providing 115+ tools to read courses, assignments, submissions, rubrics, quizzes; grade, comment, manage course content, and handle Canvas admin workflows from any AI agent.163686 npm6MIT
- 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
TDQS
Scored across 19 tools
Each tool targets a distinct resource or action: course_content maps structure, list_files/read_file handle files, get_page/get_syllabus retrieve specific content, read_discussion/post_discussion_reply handle discussions, and list_assignments/get_assignment/my_submission/submit_assignment cover assignment workflows. Even similarly themed tools like course_content and list_files are clearly differentiated by their descriptions.
Most tools follow a verb_noun pattern (list_files, get_page, read_discussion, submit_assignment), and there are consistent prefixes like my_ (my_courses, my_grades) and course_ (course_content, course_announcements). However, some names deviate from the dominant pattern (course_content, canvas_request, whats_due, whoami), making the naming slightly inconsistent.
With 19 tools, the server is on the heavier end but appropriate for a Canvas LMS integration. The tools cover a wide range of resources—courses, files, pages, assignments, discussions, grades, and submissions—without being redundant or overwhelming. The count feels justified by the breadth of the domain.
The tool set covers the primary student-facing workflows: discovering courses, viewing content, checking due dates and grades, reading and posting to discussions, and submitting assignments. There are minor gaps like no direct file upload tool, but the generic canvas_request and search_canvas_api tools provide an effective fallback for any missing operations.