mcp-moodle-teacher
It is a read-first MCP server for Moodle staff: lecturers can see their courses, students, submissions, gradebooks, attendance and timetables; academic office staff can run cross-course checks, process lecturers' grade files into gradebook imports, and make a few clearly-labeled, confirmation-required writes.
Identity & capabilities:
whoamiandlist_functionsshow who the token belongs to and which Moodle web-service functions are available.Courses & content: list your courses, their sections/modules, enrolled students with roles/emails/last access, and announcements.
Assignments & submissions: list assignments, who submitted what, per-student submission status, and who is missing a deadline.
Grades & feedback: read the gradebook and write a mark/feedback on one submission (
grade_submission), or post a course announcement (announce).Attendance: read attendance sessions and per-student presence/absence reports, and change one student's status in a session (
mark_attendance).Timetable: generate a week timetable across campus, detect room/lecturer clashes, produce a WhatsApp message and optionally save an HTML timetable page.
Academic-office tools: find late attendance registers, identify students at risk across multiple courses, and check/convert/verify lecturers' spreadsheet grade files into Moodle-gradebook CSVs.
Writing tools are explicit:
grade_submission,announce, andmark_attendancechange Moodle data and are meant to be confirmed before use; everything else is read-only.
Provides tools for teachers to manage Moodle courses, including viewing enrolled students, assignments, submissions, missing work, gradebook items, and announcements, as well as grading submissions and posting announcements.
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., "@mcp-moodle-teacher Who hasn't submitted the essay yet?"
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.
mcp-moodle-staff
An MCP server that gives an AI assistant the staff side of Moodle — for the lecturer marking their own course and for the academic office running a whole campus: who is enrolled, who submitted, who has been absent, which registers are late, which students are struggling in more than one course, the week's rooms, and the lecturers' grade files turned into gradebook imports.
The Moodle MCP servers published so far are written from the student's seat: my courses, my grades, my deadlines. This one is for the people on the other side of the desk. Read-first; every tool that changes Moodle says so and asks for confirmation.
Tested against Moodle 4.5 with the standard moodle_mobile_app web service.
Not comfortable with a terminal? There is nothing to type: install it as an extension, with pictures.
What it does
Reading
Tool | Answers |
| who the token belongs to, which Moodle, and what that token may do |
| every web-service function your token is allowed to call |
| your courses, with the id every other tool needs |
| who is enrolled: role, email, city, last access |
| sections and modules as the students see them |
| assignments with due date, maximum grade, and the brief as plain text |
| who submitted what, with file names and download URLs |
| one student on one assignment: state, grade, feedback, extension |
| enrolled students who have not submitted — the morning-after list |
| grade items with marks and feedback |
| recent posts in the course news forum |
| the sessions of each attendance register: date, duration, whether taken |
| presences and absences per student, excused apart, with an optional absence limit |
The week's timetable — timetable reads every lesson of a campus for one
week (lessons are attendance sessions, which Moodle shows as calendar events),
with lecturers and number of students from the enrolments and the room from the
session description (Aula: DREAM). It reports room clashes, a lecturer in two
places and lessons with no room, writes the week as a WhatsApp message, and can
save it as a web page: a timeline per room, each lecturer's own view, free rooms.
Ready-made requests — in Claude Desktop they appear in the menu, so nobody has to write a prompt: Orario della settimana, Carica i voti dei professori, Controllo presenze del venerdì, Registri presenze in ritardo, Studenti a rischio (in Italian, for the academic office in Florence; see the guide).
Across courses, for the academic office
Tool | Answers |
| registers not taken within 24 hours of the lesson (the ESE rule), grouped by lecturer: overdue, taken late, still in time |
| one row per student across every course: absences over the limit, assignments not handed in, failing marks; trouble in two courses or of two kinds ranks first |
Lecturers' grade files — for the academic office that enters marks sent in by lecturers as spreadsheets (one file per module, a matriculation number and a mark per student for each assessment).
Tool | Does |
| reads a file or a whole folder: which course each file points at (from its name), which gradebook item each column goes to, and which rows are ready or blocked — mark not a number, student not enrolled in that course, same student twice |
| writes one CSV per file for Moodle's gradebook import (Grades ▸ Import ▸ CSV), mark and feedback side by side, plus |
| after the import, reads the gradebook back and compares it with the lecturers' files, row by row |
Marks are copied, never computed: 57,5 and 57.5 are both 57.5, and anything
uncertain (ABS, 5 7, a cell Excel turned into a date) is reported, not guessed.
Why a CSV and not a direct write: gradebook items created by hand (the usual
"Final" and "resit") have no web service that writes them; the CSV import is
Moodle's own way in.
Writing — these change what students see, so the server's instructions tell the assistant to confirm with you before calling them.
Tool | Does |
| mark and written feedback on one submission |
| a post in the news forum; everyone enrolled is emailed |
| one student's status in one session, e.g. absent → excused after a certificate |
The attendance tools need the mod_attendance_* functions to be part of your
token's web service. On many sites they are not: whoami says so
(can_read_attendance), and the site administrator can add them.
Related MCP server: Moodle MCP Server
Lecturer or academic office
The office's tools (grade files, late registers, students at risk and their
ready-made requests) are on by default. A lecturer who only needs their own
courses unticks Staff tools in the extension's settings (or sets
MOODLE_STAFF_TOOLS=false) and sees 17 tools instead of 22.
What it deliberately does not do
Upload course materials. Moodle core has no web service that creates a module or a resource, so no MCP server can add a file to a course section. Put the materials where you already keep them (a course website, a repository) and link to them from Moodle.
Install
As a Claude Desktop extension — download mcp-moodle-staff.mcpb from the
latest release,
then Settings ▸ Extensions ▸ Install Extension… and fill in the two boxes.
Nothing else to install: Claude Desktop runs it. The
illustrated walkthrough covers this in full.
From the command line, for Codex, Claude Code or any other MCP client — it builds itself on install, so there is nothing to clone:
npx -y github:NiccoloSalvini/mcp-moodle-staffFrom a clone:
npm install && npm run build # dist/index.js
npm run bundle # dist/mcp-moodle-staff.mcpbGet a token
Your Moodle must have web services enabled. If Preferences → Security keys
exists for your account, copy the token for Moodle mobile web service. If
that page is empty — your role may lack moodle/webservice:createtoken — the
included script asks Moodle directly:
MOODLE_SITE=https://moodle.example.edu bash scripts/get-moodle-token.shIt reads the password with read -s, never echoes it, never stores it and never
puts it on a command line. It writes .env with mode 600.
Use the exact base URL Moodle knows itself by. If you get
requirecorrectaccess, you have the wrong host — try it with and without www.
Configure your MCP client
{
"mcpServers": {
"moodle": {
"command": "npx",
"args": ["-y", "github:NiccoloSalvini/mcp-moodle-staff"],
"env": {
"MOODLE_URL": "https://moodle.example.edu/webservice/rest/server.php",
"MOODLE_TOKEN": "${MOODLE_TOKEN}"
}
}
}
}For Codex, one line does it:
codex mcp add moodle --env MOODLE_URL=… --env MOODLE_TOKEN=… -- npx -y github:NiccoloSalvini/mcp-moodle-staffExport MOODLE_TOKEN in the shell that launches the client (set -a; . .env; set +a)
rather than writing it into the JSON, so the credential stays out of version control.
Then ask whoami first. It reports how many functions your token can reach and
whether grading and posting are among them; most failures are a permission the
site has not granted, not a bug.
Handling the token
A Moodle web-service token is a bearer credential carrying all of your rights, including marking. Treat it as a password:
It is sent in the POST body, never in the query string, because URLs are written to proxy logs, to the server's access log and to any client's request log.
Transport and Moodle errors are redacted before they become messages.
Installed as an extension, the token goes in a field marked sensitive: the app stores it, and it never appears in a configuration file you might share.
.envis gitignored and written with mode 600.If a token is exposed, revoke it in Preferences → Security keys (or ask your admin to delete it) and fetch a new one. Requesting a token again returns the same one until the old is deleted.
Personal data
These tools return real names, email addresses and submitted work. Anything an assistant sees can end up in a transcript. Ask for the aggregate — how many are missing, which one is at risk — before you ask for the list.
Licence
MIT.
Available Tools
22 toolsannounceA
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.
Inputs: message (required), subject (required), courseid (required), pinned.
announcementsB
Recent announcements in the course's news forum, newest first.
Inputs: courseid (required), limit.
assignmentsC
Assignments in a course: the assignid the submission tools need, the due date, the maximum grade and the brief as plain text.
Inputs: courseid (required).
attendance_reportA
Presences and absences per student across every session already taken: a count for each status (present, late, excused, absent, as the register names them), the list of dates missed, and a flag for whoever has reached the absence limit. Sessions not yet taken are ignored. Excused absences are counted apart from unexcused ones.
Inputs: courseid (required), absent, excused, max_absences, +1 more.
attendance_sessionsA
The sessions of every attendance register in a course: date, duration, whether the register has been taken, and how many students were marked. The sessionid is what mark_attendance expects.
Inputs: courseid (required).
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.
Inputs: courseid (required).
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.
Inputs: courseid (required), userid.
grades_checkA
Reads only. For each lecturer's grade file (or every file in a folder): which Moodle course its name points at, which gradebook item each mark column goes to (Final, resit, ...) and where the feedback goes (Evaluation / Feedback ...), and for every student whether the row is ready or blocked, with the reason (not a number, student not enrolled in that course, duplicate row...). Also lists enrolled students missing from the file. Marks written 57,5 or 57.5 are both read as 57.5.
Inputs: path (required), items, courseid.
grades_csvA
Writes files, not Moodle. For each lecturer's file, a CSV ready for Moodle's gradebook import (Grades > Import > CSV file) into the right course: one row per ready student, identified by ID number, with the mark and — always next to it, since Moodle wipes a grade imported without it — the feedback. Blocked rows go to _to_check.csv with the reason, for the academic office to raise with the lecturer. Marks are written with a decimal point, exactly as the lecturer gave them.
Inputs: path (required), out_dir (required), items, courseid.
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.
Inputs: grade (required), userid (required), assignid (required), attempt, +2 more.
grades_verifyA
The double check after the import, reads only: for every ready row in the lecturer's file(s), read what Moodle's gradebook now holds for that student on that item and compare, mark and feedback. Needs a token allowed to read the user grade report (the academic office; a lecturer's token usually is not).
Inputs: path (required), items, courseid.
late_registersB
Attendance registers not taken within the hours the rules allow (ESE: 24 hours from the end of the lesson), across every course that matches, grouped by lecturer: overdue (still not taken), taken late, and pending (lesson over, still in time). Needs the mod_attendance_* functions in the token's service.
Inputs: days, hours, search.
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.
Inputs: contains.
mark_attendanceA
WRITES TO MOODLE, visible to the student in their attendance record. Set one student's status in one session (e.g. turn an absence into excused after a medical certificate). statusid comes from attendance_sessions. Confirm with the user first.
Inputs: userid (required), statusid (required), sessionid (required).
missingA
Students enrolled in the course who have not submitted this assignment. The list to look at on the morning after a deadline.
Inputs: assignid (required), courseid (required).
my_coursesA
The courses this account is enrolled in, with the id every other tool needs.
Inputs: no named parameters.
studentsA
Everyone enrolled in a course, with their role, email and last access. The userid returned here is what grade_submission expects.
Inputs: courseid (required).
students_at_riskA
One list per student across every course that matches: absences at or over the limit, assignments past their due date and not handed in, and failing marks (below the pass mark, on assignments and on gradebook items such as Final). A student with trouble in two or more courses, or of two kinds, ranks first. Each source says whether it could be read: a lecturer's token usually cannot read the gradebook, and attendance needs the mod_attendance_* functions.
Inputs: search, pass_mark, max_absences, lates_per_absence.
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.
Inputs: assignid (required), only_submitted.
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.
Inputs: userid (required), assignid (required).
timetableA
The lessons of one week across a campus, from Moodle: day, time, room, course, lecturers and number of students, plus room clashes, a lecturer in two places, lessons with no room yet, and the week as a WhatsApp message. The room is read from the attendance session description ('Aula: DREAM'). With page_path it also writes the week as a web page (per room, per lecturer, free rooms) to open in a browser.
Inputs: week, search, lecturer, page_path.
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.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 22 tools
Each tool targets a distinct resource or action: attendance sessions, attendance reports, late registers, and marking are clearly separated; the grade-import tools (check/csv/verify) are also distinct. Even the most similar tools, submissions and submission_status, are disambiguated by their descriptions.
All names use lowercase snake_case and are readable, but the convention is mixed: many read tools are bare nouns (students, assignments, announcements), while others use verb_noun (mark_attendance, list_functions) or noun_verb (grades_check, grades_verify). There is no consistent verb-first pattern across the set.
At 22 tools, the set sits in the 'borderline heavy' range. Each tool appears purposeful and none feel redundant, but the count is high enough that an agent will need to navigate a large surface for what is mostly attendance, grading, and reporting workflows.
The core teacher workflows are well covered: attendance tracking and marking, assignment submissions and grading, grade-file import verification, announcements, and student risk summaries. Minor gaps exist—for example, no bulk attendance-taking tool or assignment creation/update—but they do not break the main intended workflows.
Maintenance
Related MCP Connectors
Create, edit, translate, and export SCORM eLearning modules from a connected AI assistant.
Run the Geduk LMS from an AI assistant: courses, sessions, enrolments, users and catalogue.
Teachable MCP server for ChatGPT, Claude and any AI agent: update lecture, create coupon, send email, reply to comment and list enrollments in your own Teachable account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Teachable yourself; Cotlet does not store your password and you need no Teachable API key. About the official Teachable API: Teachable has a public API, but only on the Growth plan and up, and it reads courses and lecture content and manages users, enrollments, pricing plans and transactions (checked 11 Oct 2026). Lesson editing, coupons, emails to students and comments are not in it. Setup and FAQ: https://cotlet.dev/integrations/teachable-api-mcp-server
Udemy MCP server for ChatGPT, Claude and any AI agent: create coupon, update course, send announcement and get revenue report in your own Udemy account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Udemy yourself; Cotlet does not store your password and you need no Udemy API key. About the official Udemy API: Udemy has an Instructor API that lists your courses, reads reviews, and reads and answers Q&A questions and direct messages (checked 12 Oct 2026). It has no coupons, announcements, review responses, course edits or revenue. Setup and FAQ: https://cotlet.dev/integrations/udemy-api-mcp-server
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with Moodle via web services, allowing tasks like listing courses, assignments, events, and downloading files.104MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Moodle LMS via browser automation, using a server and browser extension to keep credentials local and route commands securely.10 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Moodle LMS via the Moodle REST API, supporting management of courses, users, enrollments, grades, and content.1GPL 3.0
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to read your Moodle courses, list materials, quizzes, and search content to plan exam preparation through natural language.1-