quercus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QUERCUS_BASE_URL | Yes | The Canvas API base URL for your institution, e.g. https://q.utoronto.ca/api/v1 | |
| QUERCUS_API_TOKEN | Yes | Your Quercus access token. Treat this like a password; it grants read access to your account. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_coursesC | List the user's Quercus courses. |
| list_assignmentsC | List assignments for a given Quercus course, optionally filtered by bucket. |
| get_course_gradesC | Get the current user's grades/enrollment info for a specific course. |
| list_all_gradesA | List the current user's enrollments and grades across all active courses. |
| list_announcementsC | List announcements for one or more courses (context_codes like 'course_12345'). |
| list_todoA | List the current user's Quercus to-do items (ungraded submissions, upcoming quizzes, etc.). |
| list_upcoming_eventsB | List the current user's upcoming Quercus events and assignment due dates. |
| list_calendar_eventsB | List calendar events/assignments in a date range across given course context codes. |
| list_filesC | List files available in a Quercus course. |
| get_file_download_urlB | Resolve a Quercus file ID to its metadata and authenticated download URL. |
| get_course_modulesC | List the modules (and items) for a Quercus course. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools target distinct resources (courses, assignments, grades, announcements, files, modules). The only meaningful overlap is between list_upcoming_events and list_calendar_events, both of which return events/assignment due dates, though descriptions clarify one is upcoming and the other is a custom date range.
Every tool uses snake_case with a consistent verb_noun pattern: all are either list_* or get_* prefixed. The convention is applied uniformly across all 11 tools.
11 tools is a well-scoped set for a Quercus integration, covering the main read-only resources without unnecessary bloat. Each tool has a clear purpose.
The surface is entirely read-only (list/get) and lacks any create, update, or delete operations, such as submitting assignments, posting to discussions, or uploading files. While read coverage is solid, these are notable gaps for an LMS agent.