Moodle MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOODLE_DEBUG | No | Set to 1 for request-level logs on stderr | |
| MOODLE_NO_BIND | No | Set to 1 to never bind a source address | |
| MOODLE_SERVICE | No | Web Services shortname used for the token | moodle_mobile_app |
| MOODLE_BASE_URL | No | Moodle site root, no trailing slash (used when baseUrl is not set in .secrets/moodle.json) | https://online.mospolytech.ru |
| MOODLE_DATA_DIR | No | Where downloaded course material goes | ./moodle-data |
| MOODLE_LOCAL_ADDR | No | Source address to bind sockets to, to bypass a VPN tunnel | auto (en0, en1) |
| MOODLE_SECRETS_DIR | No | Where moodle.json (credentials) and the token cache live | ./.secrets |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| moodle_whoamiA | Signed-in user: full name, user id, site name/release and the number of API functions available. |
| moodle_coursesA | List my enrolled courses as "id — fullname (shortname)". Start here: every other tool needs a course id or a module id taken from it. |
| moodle_course_structureA | Course outline as markdown: sections, every module (assignment, file, page, url) with its type, due dates and attached files. Use it to see what the course contains before downloading anything. |
| moodle_course_moduleA | One course module by cmid — the numeric id= in a Moodle URL such as /mod/assign/view.php?id=12345. Returns name, type, course id and, for assignments, the due date and description. |
| moodle_assignmentC | Full assignment: description, due/cutoff dates, max grade, attachments with download URLs, and my submission status (new/draft/submitted, graded or not, can I still submit). |
| moodle_list_filesA | Every downloadable file in a course: section, module, filename, size and a direct fileurl. Pass that url to moodle_download_file. |
| moodle_download_fileA | Download one file into the local moodle-data/downloads folder and return its path. Takes a fileurl from moodle_list_files or an assignment attachment. |
| moodle_dump_courseA | Mirror a whole course to disk: structure.md, course.json, every file and every assignment with its description and attachments. Saved to moodle-data/. Idempotent — already downloaded files are skipped by size. |
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 8 tools
Most tools have clearly distinct roles: discovery (whoami, courses), inspection (structure, module, assignment), and downloading (list_files, download_file, dump_course). There is some natural overlap between course_structure/course_module and list_files/dump_course, but the descriptions explicitly explain when to use each and how they chain together.
All names use the same lowercase snake_case style with a consistent moodle_ prefix, which makes them easy to scan and group. The suffix pattern is not strictly verb_noun throughout (whoami, courses, assignment are noun-like), but the overall convention is predictable.
Eight tools is well-scoped for a Moodle course-content server, with separate tools for authentication, course discovery, structure inspection, file listing, single-file download, and bulk mirroring. Each tool appears to earn its place without excessive fragmentation.
The read/download lifecycle is well covered: user context, courses, structure, modules, assignments, files, single downloads, and full-course mirroring. Minor gaps remain around write/submission actions and broader Moodle areas like grades or forums, especially since moodle_assignment reports whether the user can still submit but provides no way to submit.