Canvas LMS MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Canvas LMS MCP Server Show my current grades and upcoming assignments"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Canvas LMS MCP Server
A Model Context Protocol server that gives an MCP client (Claude Desktop, Claude Code, or anything else that speaks MCP) read-only access to your Canvas LMS account.
It answers two questions:
"What am I taking and how am I doing?" — active courses with current grades.
"What do I still owe and when is it due?" — outstanding assignments with due dates.
Communication uses the standard stdio transport, so the client launches the server as a subprocess. Nothing is written to stdout except MCP traffic.
Requirements
Node.js 18.17 or newer (the server uses the built-in
fetch)A Canvas personal access token
Related MCP server: Canvas MCP Server
Install
cd canvas-mcp-server
npm installConfiguration
Both variables are required; the server exits with a clear message if either is missing.
Variable | Description | Example |
| Your Canvas instance root. A trailing |
|
| A Canvas personal access token. |
|
Getting a Canvas access token
Log in to Canvas.
Go to Account → Settings.
Under Approved Integrations, click + New Access Token.
Give it a purpose and (optionally) an expiry date, then click Generate Token.
Copy the token immediately — Canvas shows it only once.
The token carries your full Canvas privileges. Keep it out of version control, and revoke it from the same settings page if it ever leaks.
Connecting a client
Add the server to your MCP client config, pointing at the absolute path of
src/index.js:
{
"mcpServers": {
"canvas": {
"command": "node",
"args": ["/absolute/path/to/canvas-mcp-server/src/index.js"],
"env": {
"CANVAS_API_URL": "https://asu.instructure.com",
"CANVAS_ACCESS_TOKEN": "your-token-here"
}
}
}
}Claude Desktop —
claude_desktop_config.json(macOS:~/Library/Application Support/Claude/, Windows:%APPDATA%\Claude\).Claude Code —
claude mcp add canvas --env CANVAS_API_URL=... --env CANVAS_ACCESS_TOKEN=... -- node /absolute/path/to/canvas-mcp-server/src/index.js
Restart the client after editing the config.
Tools
list_courses_and_grades
Every course you are actively enrolled in as a student, with its current grade.
Parameter | Type | Default | Description |
| boolean |
| Also include active enrollments from terms that have already ended. |
Canvas reports grades twice when your institution uses grading periods: once for
the period in progress and once for the whole course. The grades.scope field
says which one you are looking at:
current_grading_period— the score covers the grading period in progress, andcourse_total_score/course_total_gradecarry the whole-course numbers.course_total— the institution does not use grading periods, so the score is the course total.unavailable— Canvas returned no enrollment with grade data.
Within either scope, current_* ignores work that has not been graded yet, while
final_* counts ungraded work as a zero.
{
"courses": [
{
"id": "101",
"name": "Full Stack Web Development",
"course_code": "GIT-411",
"term": "Fall 2026",
"term_start": "2026-08-20T00:00:00Z",
"term_end": "2026-12-18T00:00:00Z",
"enrollment_state": "active",
"grades": {
"current_score": 88.0,
"current_grade": "B+",
"final_score": 80.5,
"final_grade": "B-",
"scope": "current_grading_period",
"grading_period_title": "Fall Term",
"course_total_score": 91.4,
"course_total_grade": "A-"
},
"html_url": "https://asu.instructure.com/courses/101"
}
],
"course_count": 1,
"retrieved_at": "2026-09-01T12:00:00.000Z"
}list_upcoming_assignments
Assignments across your active courses that are still outstanding, sorted by due date, soonest first.
Parameter | Type | Default | Description |
| integer 1–365, or |
| How far ahead to look. |
| boolean |
| Include past-due work that was never turned in. |
| boolean |
| Include outstanding work with no due date. |
| string[] | all active courses | Restrict to specific Canvas course IDs. |
An assignment counts as outstanding when it is published, gradable, and not submitted, graded, or excused. Concretely, these are filtered out:
anything with a submission timestamp
submissions in
submitted,pending_review, orgradedstateexcused assignments
assignments that already carry a score or grade (manual or on-paper entry)
not_gradedassignments (attendance placeholders and the like)unpublished assignments
{
"assignments": [
{
"id": "9004",
"name": "Missed lab writeup",
"course_id": "101",
"course_name": "Full Stack Web Development",
"due_at": "2026-08-28T06:59:00.000Z",
"days_until_due": -4.2,
"overdue": true,
"points_possible": 25,
"submission_types": ["online_upload"],
"submission_state": "unsubmitted",
"missing": true,
"locked": false,
"unlock_at": null,
"lock_at": null,
"html_url": "https://asu.instructure.com/courses/101/assignments/9004"
}
],
"assignment_count": 1,
"courses_checked": 2,
"window": {
"from": "2026-09-01T12:00:00.000Z",
"to": "2026-09-15T12:00:00.000Z",
"include_overdue": true,
"include_undated": false
},
"errors": [],
"retrieved_at": "2026-09-01T12:00:00.000Z"
}If one course cannot be read — concluded, restricted, or otherwise erroring — it
is listed in errors and the remaining courses still return results.
Notes on behavior
Pagination. Canvas paginates every collection via the
Linkheader. The client followsrel="next"at 100 records per page, capped at 20 pages per endpoint so a bad response cannot loop forever.Concurrency. Assignments are fetched from at most 5 courses at a time to stay clear of Canvas rate limits.
Current term. By default only courses whose term has not ended are returned. Canvas's default term has no end date and is always included.
Errors. Canvas failures come back as MCP tool errors carrying the status code and Canvas's own message, with a hint for the common cases (401 → bad token, 404 → wrong URL).
Read-only. Both tools are annotated
readOnlyHint. The server issues onlyGETrequests and never modifies your Canvas data.
Development
npm test # 36 tests: API client, grade logic, filtering, and an end-to-end MCP round tripThe suite uses a fetch stand-in with recorded Canvas payloads, so no network or
real token is needed. All fixture dates are relative to the moment the tests run.
src/
index.js MCP server: tool definitions, schemas, stdio wiring
canvas.js Canvas REST client: auth, pagination, error mapping
courses.js Active-course and grade normalization
assignments.js Outstanding-assignment filtering and due-date windowsLicense
MIT
Available Tools
2 toolslist_courses_and_gradesList active courses and gradesARead-only
Fetch every course the user is actively enrolled in as a student, together with the current grade for each. When the institution uses grading periods, the score reported is for the grading period in progress and the whole-course total is included alongside it (see the 'scope' field). Defaults to the current term only.
Inputs: include_all_terms. Returns: courses, course_count, retrieved_at
list_upcoming_assignmentsList upcoming unsubmitted assignmentsARead-only
Fetch assignments across the user's active courses that are still outstanding — not submitted, not graded, and not excused — with their due dates, sorted soonest first. Past-due work that was never turned in is included by default.
Inputs: course_ids, days_ahead, include_overdue, include_undated. Returns: errors, window, assignments, retrieved_at, +2 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools serve clearly distinct purposes: one retrieves course enrollments with grades, the other retrieves upcoming assignments. There is no ambiguity in selecting between them.
Both tools follow a consistent 'list_' prefix followed by a clear noun phrase ('courses_and_grades', 'upcoming_assignments'), making the naming pattern uniform and predictable.
With only two tools, the server feels minimal but not entirely unreasonable for a focused student dashboard scope. The count is at the borderline of being thin, as agents may expect additional related operations.
The tool surface covers the two primary student needs (grades and upcoming assignments) but lacks operations like retrieving individual course details, assignment submissions, or past assignmentscars. This leaves notable gaps for broader academic workflows, though it may suffice for a narrow use case.
Maintenance
Related MCP Connectors
Manage your Canvas coursework with quick access to courses, assignments, and grades. Track upcomin…
Read-only access to Epivo's live course catalogue for AI agents.
Read-only access to a student's recorded classes: transcripts, notes, slides and concept map.
Read your plat.plus courses, tasks, course pages, sessions, files and messages. Read-only.
Related MCP Servers
- FlicenseAqualityNot gradedmaintenanceEnables interaction with Canvas LMS courses and assignments directly from your LLM, allowing you to retrieve, search, and summarize course information, check due dates, and access assignment details without leaving your AI assistant.43,290 npm-
- FlicenseBqualityNot gradedmaintenanceProvides read-only access to Canvas LMS for students to retrieve courses, assignments, grades, files, discussions, and planner items. Includes optional NotebookLM integration for uploading course content to AI-powered study notebooks.453,290 npm-
- AlicenseAqualityDmaintenanceEnables AI systems to interact with Canvas Learning Management System data, allowing users to access courses, assignments, quizzes, planner items, files, and syllabi through natural language queries.2242 PyPI7MIT
- FlicenseBqualityDmaintenanceEnables interaction with Canvas LMS to access courses, modules, files, pages, assignments, submissions, announcements, upcoming deadlines, and syllabus.15-