The Model Context Protocol is an open standard that lets an AI client — a desktop app, a web chat, an IDE assistant — connect to tools and data directly. moodle-cli and edstem-cli each ship an MCP server so a client that can’t run their commands itself can still read your units, deadlines, grades and discussions. OnTrack has no MCP server in this release. ontrack is CLI-only; see /ontrack/index.

​
Your options

Uploading assignment files (submit) only works from the “on your computer” Moodle option, because the files are on your computer. Every other Moodle tool is the same on every option. Posting to Ed is off until you turn it on; a posting tool then fails with a clear message instead of disappearing.

​
Is it safe?

Your Moodle sign-in or Ed token never leaves your control: a local server reads it from your own computer, and a remote server keeps it encrypted in your own private deployment, not a shared one. Every surface can only see what your own account can already see — there’s no separate service account with broader access. Nothing connects until you approve it yourself, whether that’s pasting a token you generated or approving a one-time pairing code in your browser. If you ever want to cut a client off, revoking it stops its access immediately. See Security for exactly what’s stored, what’s logged, and how to rotate or revoke access.

​
Which page to read

1

Find your client

2

Pick a surface for each product

Moodle: run moodle mcp connect <client> and let it set up the bridge. Ed Discussion: use the on-your-computer option if the app can start local programs, and the hosted service otherwise.
3

Verify the connection

Each client page ends with the exact command or menu to confirm the server connected and to list its tools.