ontrack is a terminal client for OnTrack. It works for students checking what is due, teaching staff triaging a cohort, scripts run on a schedule, and agents acting on a person’s behalf. Scripting this or building an agent integration? See OnTrack CLI for scripts and agents.
There is no MCP (Model Context Protocol) server for OnTrack in this release. Every integration goes through the ontrack binary and its --json output. See Choose a surface for how this compares to the Moodle and Ed Discussion MCP servers.

​
What it reads

  • Enrolled units (and, for teaching staff, unit roles) — units, roles
  • Tasks in a unit: status, due dates, target grade, submitted grade — tasks
  • A task sheet, converted from its source PDF to Markdown — tasks read
  • Task resources and whole-unit resource archives — units get, tasks get
  • Task chat history (tutor and student comments) — chats
  • The signed-in identity — user

​
What it writes

  • A task’s self-reported workflow state (not_started, working_on_it, need_help) — tasks set
  • Task file submissions — tasks submit
  • Chat messages on a task — chats send
  • Chat read state — chats mark-read, and chats read as a side effect of fetching history
Every write prints a plan first. See Mutations for the --yes and --dry-run model every tool in this family shares.

Install

Get ontrack on your machine and point it at your site.

Sign in

Reuse a browser session or sign in through SAML.

Units and tasks

List units, read task sheets, filter by status.

Chats

Read tutor feedback and send messages on a task.