mcp-moodle-teacher
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOODLE_URL | Yes | The base URL of the Moodle web service endpoint, e.g. https://moodle.example.edu/webservice/rest/server.php | |
| MOODLE_TOKEN | Yes | Your Moodle web service token, a bearer credential with your full rights |
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 |
|---|---|
| whoamiA | Who the token belongs to, which Moodle it points at, and how many web-service functions that token is allowed to call. Run this first when something fails. |
| list_functionsA | Every web-service function this token may call, optionally filtered by a substring (e.g. "assign", "forum", "grade"). Use it to find out what this Moodle actually allows before assuming a tool is missing. |
| my_coursesA | The courses this account is enrolled in, with the id every other tool needs. |
| studentsA | Everyone enrolled in a course, with their role, email and last access. The userid returned here is what grade_submission expects. |
| course_contentsB | Sections of a course and the modules in each one: what the students see, in the order they see it. The 'cmid' identifies an activity. |
| assignmentsC | Assignments in a course: the assignid the submission tools need, the due date, the maximum grade and the brief as plain text. |
| submissionsC | Who handed in what for one assignment: the userid, the status ('submitted', 'new', 'draft'), when it arrived, the file names with download URLs and any online text. |
| submission_statusA | The full picture for one student on one assignment: submission state, whether it is locked, the current grade, any feedback already given and any extension. |
| missingA | Students enrolled in the course who have not submitted this assignment. The list to look at on the morning after a deadline. |
| gradebookB | Grade items for a course, for one student or for everyone the token can see. Shows what has a mark and what is still empty. |
| grade_submissionA | WRITES TO MOODLE, visible to the student. Put a mark and written feedback on one submission. The grade is on the assignment's own scale (see assignments); pass -1 to leave the mark unchanged and only update the feedback. This overwrites whatever mark and comment were there before, so confirm the numbers with the user first. |
| announceA | WRITES TO MOODLE and emails everyone enrolled. Post an announcement in the course's news forum. Check the wording with the user before calling this. |
| announcementsB | Recent announcements in the course's news forum, newest first. |
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 13 tools
Every tool targets a distinct resource or action: identities, course lists, rosters, content, assignments, submissions, per-student status, missing students, gradebook, grading, and announcements. Even the similar-sounding announce/announcements are cleanly separated as write versus read.
Names are readable and all lowercase with underscores, but they mix conventions: plural nouns (students, assignments, submissions), verb phrases (list_functions, grade_submission, announce), adjectives (missing), and idiosyncratic names (whoami, my_courses). The pattern is not consistent enough to predict tool names reliably.
Thirteen tools is a well-scoped size for a Moodle teacher assistant. Each tool covers a meaningful step in the main workflows of reviewing courses, handling assignments and submissions, grading, and communicating with students.
The core teacher workflows are well covered: course discovery, student lookup, content inspection, assignment and submission review, missing submissions, gradebook viewing, grading, and announcements. Minor gaps exist, such as no assignment creation, no feedback file upload, and no announcement editing, but these do not create dead ends for the stated teaching-focused purpose.