Moodle Mcp

io.github.av-leschinskiyPublished by GitHub account av-leschinskiyv0.2.1Updated Oct 30, 2026

Moodle MCP server for teachers: review assignment submissions, grade and give feedback; SSO login

Overview

AI-generated overview

Moodle MCP server for teachers: lets an assistant browse courses, review student submissions, download files, and save grades with feedback.

What you can do
  • Inspect the site and courses: who you are, Moodle version, available functions, your courses
  • Review assignments and submissions: list assignments, participants and submission statuses, pending work, and a full submission
  • Download submission files to local disk
  • Grade and give feedback: save a grade with feedback, add a submission comment, return a submission to draft (each requires confirmation)
When to use it
Useful for teachers on a Moodle site who want an assistant to help triage pending submissions, read student work, and record grades and feedback without clicking through the web interface.
Requirements
Local stdio process via npx, Node.js 22 or newer. MOODLE_URL is required. Google Chrome or Chromium for the separate login command, which opens a browser window for SSO and captcha. The Moodle site must have mobile app web services enabled. The token is saved to a file (MOODLE_TOKEN_FILE) or can be supplied via MOODLE_TOKEN.
Before you install
Acts as the teacher account: it can save grades, post comments students see, and return submissions to draft, though the host asks for confirmation on those writes. Downloading files writes to local disk. A login token is stored on disk and a separate Chrome profile keeps site cookies, so logging in again may not need a password. MOODLE_TOKEN is a secret; keep it out of shared configs.

Installation

In SourceWeft

  1. Open Moodle Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Moodle MCP Server

An MCP server for AI assistants (Claude Code, Cursor, Codex and other stdio clients) on top of the Moodle web services REST API. It is built for teachers: the assistant can see courses, assignments and student submissions, download submission files, and save a grade with feedback, acting as the teacher and only after the teacher confirms. Unlike student-oriented Moodle MCP servers, the focus here is reviewing assignments and grading.

The server works with any Moodle site that has the mobile web service (moodle_mobile_app) enabled: the token is issued the same way as for the Moodle mobile app, so login through an external OAuth provider with a captcha works too.

Prerequisites

  • Node.js ≥ 22.
  • Google Chrome or Chromium, for the moodle-mcp-login command.
  • Mobile app access enabled on the Moodle site (Site administration → Mobile app). To check: <site>/admin/tool/mobile/launch.php should open rather than return an error.

Quick start

The example below uses https://moodle.example.org; replace it with your Moodle address exactly as it appears in the browser (scheme, host, path; a trailing slash does not matter).

  1. Log in, once per machine and again whenever a tool returns a login error (Moodle login and server token, in Russian):

    bash
    MOODLE_URL=https://moodle.example.org npx -y -p @av-leschinskiy/moodle-mcp moodle-mcp-login

    A Chrome window opens: log in to the site as usual and solve the captcha yourself. The command prints Logged in as <name> on <site> and closes the window. Without -p, npx would start the server instead of the login command. Chrome is looked up in PATH; on macOS and Windows, set its path in MOODLE_CHROME.

  2. Add the server to your client. Claude Code:

    bash
    claude mcp add moodle -e MOODLE_URL=https://moodle.example.org -- npx -y @av-leschinskiy/moodle-mcp

    Add -s user to enable it for all projects; without it, only for the current one.

    Codex, with a command or a block in ~/.codex/config.toml:

    bash
    codex mcp add moodle --env MOODLE_URL=https://moodle.example.org -- npx -y @av-leschinskiy/moodle-mcp
    toml
    [mcp_servers.moodle]command = "npx"args = ["-y", "@av-leschinskiy/moodle-mcp"]env = { MOODLE_URL = "https://moodle.example.org" }

    Cursor and other clients: a stdio server with the command npx -y @av-leschinskiy/moodle-mcp and the MOODLE_URL variable:

    json
    {  "mcpServers": {    "moodle": {      "command": "npx",      "args": ["-y", "@av-leschinskiy/moodle-mcp"],      "env": { "MOODLE_URL": "https://moodle.example.org" }    }  }}
  3. Check: ask the assistant "show my Moodle courses".

From a repository clone, use node <clone>/dist/index.js and node <clone>/dist/cli/login.js instead of npx: dist/ is committed, no build is needed.

What's inside

10 tools in total; 3 of them require user confirmation.

CategoryToolsConfirmationCovers
Site2—who I am, Moodle version, available functions, my courses
Assignments and submissions4—course assignments, participants and submission statuses, what needs the teacher across a course, full submission
Files1—downloading submission files to disk
Grading33grade and feedback, submission comment, returning a submission for rework
Full list of names

Site

  • moodle_list_courses
  • moodle_site_info

Assignments and submissions

  • moodle_get_submission
  • moodle_list_assignments
  • moodle_list_pending_submissions
  • moodle_list_submissions

Files

  • moodle_download_file

Grading

  • moodle_add_submission_comment — confirmation
  • moodle_revert_submission_to_draft — confirmation
  • moodle_save_grade — confirmation

The server acts on your behalf: it sees and changes the same things you do in the Moodle interface. The host asks for confirmation only for writes that students will see: a grade with feedback, a submission comment, returning a submission to draft (destructiveHint: true). Downloading a file also writes, but only to your disk, and needs no confirmation.

Responses are trimmed for the model context: HTML in descriptions and submissions is converted to plain text, times to ISO, a grade that is not set to null, and participant emails are never returned.

Configuration

VariableRequiredDefaultDescription
MOODLE_URLyes—Moodle site address (wwwroot), e.g. https://moodle.example.org
MOODLE_TOKEN_FILE—~/.config/mcp-moodle/token.jsonWhere moodle-mcp-login saves the token (path is resolved via homedir())
MOODLE_TOKEN——Web service token override (CI / smoke tests)
MOODLE_TIMEOUT—30000Timeout of a single API request (ms)
MOODLE_CHROME——Chrome/Chromium binary for moodle-mcp-login (looked up in PATH by default)
MOODLE_DEBUG—false1/true/yes/on enables debug output to stderr and debug level in the host log channel

The token file has 0600 permissions and stores the site address it was issued for: if it does not match MOODLE_URL, the server asks you to run moodle-mcp-login. The server reads the file on every request, so there is no need to restart the host after logging in again. The token is scrubbed from error messages, logs and tool responses (including file URLs).

The Chrome profile used for login is kept separate from your main one (~/.config/mcp-moodle/chrome-profile): site cookies persist, so logging in again often works without a password.

Development

bash
npm install        # also enables the git hooks (.githooks)npm run dev        # tsx, no compilationnpm run build      # native TypeScript 7 → dist/npm run verify     # typecheck + lint + tests + docs checkMOODLE_URL=… npm run smoke   # read-only tool chain against a live Moodle

Build only with npm run build: devDependencies contain two compiler versions, details. dist/ is committed; the pre-commit hook builds and stages it, bumps the patch version and regenerates the tables above. Architecture and rules are in AGENTS.md (in Russian).

Source: README.md at commit 2a9df4e

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

4
  1. v0.2.1LatestOct 30, 2026
  2. v0.2.0Oct 29, 2026
  3. v0.1.4Oct 21, 2026
  4. v0.1.3Oct 21, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts