Gradescope MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENV_FILE | No | Path to a dotenv file containing GRADESCOPE_EMAIL and GRADESCOPE_PASSWORD | |
| GRADESCOPE_EMAIL | No | Your Gradescope email address | |
| GRADESCOPE_PASSWORD | No | Your native Gradescope password |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gradescope_list_coursesA | List Gradescope courses grouped by student/instructor role. |
| gradescope_list_assignmentsB | List assignments for one Gradescope course.
|
| gradescope_upcoming_assignmentsB | Return upcoming assignments across all student courses, sorted by due time. |
| gradescope_list_submissionsA | List the authenticated student's own submitted assignments. If course_id is omitted, submissions from all student courses are returned. This does not download submitted files. |
| gradescope_get_submission_filesA | Return safe metadata for files in one of the authenticated student's submissions. Temporary signed Gradescope/S3 URLs are intentionally not returned. Use gradescope_download_submission_file to retrieve a file. |
| gradescope_download_submission_fileA | Download one of the authenticated student's own submitted files locally. This does not modify Gradescope. It creates a file on the machine running
the MCP server. |
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 6 tools
Each tool targets a distinct resource or action: listing courses, assignments, upcoming assignments, submissions, getting file metadata, and downloading a file. Descriptions clarify boundaries (e.g., list_assignments vs list_submissions), leaving no overlapping purposes.
All tools use a consistent gradescope_ prefix and snake_case. However, most list operations start with list_, while gradescope_upcoming_assignments breaks that pattern by not including the list_ verb, a minor deviation.
Six tools are well-scoped for a read-focused Gradescope student workflow, with each tool earning its place. No bloated or missing tools at the set level.
The set covers the core student journey: viewing courses, assignments, upcoming deadlines, submissions, and downloading submitted files. Minor gaps exist, such as no tool for detailed assignment or course metadata, but these are manageable workarounds.