This tab is for script authors, agent or integration builders, and contributors — anyone writing code against moodle, edstem or ontrack instead of typing commands at a keyboard. If you’re a student or tutor looking to install a CLI, sign in, or connect an AI app, start at the home page instead.

Shared behaviour

All three CLIs share one command model, output format, exit code scheme and mutation-confirmation rule. Learn it once here.

Command model

How every command is structured, across all three CLIs.

Output formats

How each CLI picks between a table and JSON, and how to force one.

Errors and exit codes

The exit code scheme and error shape every command follows.

Mutations

What counts as a write, and how confirmation works without a terminal attached.

Configuration

Env vars, config files and precedence, across all three CLIs.

Humans and agents

How each CLI detects who’s driving it, and what changes because of that.

Scripting each CLI

Moodle CLI

JSON shapes, exit codes and env vars for moodle.

Ed Discussion CLI

JSON shapes, exit codes and env vars for edstem.

OnTrack CLI

JSON shapes, exit codes and env vars for ontrack.

Agents

Agent skills

Generate and install the skill bundle that teaches an agent which command answers which request.

Prompting

Patterns for prompting an agent that has one of these CLIs or skills available.

MCP internals

How MCP works

What runs where, across every Moodle and Ed Discussion surface, and the result shapes tools return.

Security

Where credentials live, what gates a write, and how to revoke or rotate access.

Moodle tools

The full Moodle MCP tool catalog: arguments, result shapes, and which surface offers each one.

Ed Discussion tools

The full Ed Discussion MCP tool catalog: arguments, result shapes, and posting gates.