Tutor-MCP
Menu
Documentation / Learn and share

Learn in an institution

A shared catalogue, clear responsibilities and an individual learning path for every member.

Members, trainers and institution owners6 minLatest Tutor MCP v0.7.0Latest Tutor ACP 0.0.1
01

Give your community a shared place to learn

An institution can be a training organisation, school, team or learning community operating a Tutor service. Members find shared courses in one catalogue and continue learning through their own account.

Tutor ACP is the desktop application. Tutor MCP is the service that stores programmes, applies access rules and keeps learning state. This website introduces the software and its documentation; it does not create or host an institution for you.

If you are joining an existing organisation, start with the client installation guide. If you operate the service, follow Deploy an institution.

02

Join with your own identity

  1. Create or restore your identity in Tutor ACP, then save and confirm its encrypted backup.
  2. Give your administrator the two public keys shown by the application: your identity key and recovery key.
  3. In Settings → Institution, enter the HTTPS address supplied by your organisation, without adding /mcp.
  4. Verify the institution’s name and address, then connect once your membership is authorised.

The current institution profile does not register accounts by email or institution password. The administrator authorises the public identity; an unknown key cannot register itself or claim an owner role.

Your private keys and backup phrase stay under your control. The institution needs neither your private key nor your backup passphrase.

03

Keep responsibilities clear

Your roleWhat it enables
LearnerFind eligible courses, enroll, learn and read your own progress.
Author or authorised editorPrepare and contribute to the programmes you are allowed to edit.
TrainerSupport assigned groups and read the progress permitted by those assignments.
Pedagogy managerManage owned or assigned courses and their authorised learning workflows.
Owner or administratorManage membership, access and institution-wide responsibilities.

A programme contribution permission and an administrative role are different grants. Allowing an AI tool does not give it additional institutional rights. The server checks the account’s actual role and assignments.

Owners manage supported membership actions in Settings → Members. A staff member who wants to learn can start their own learning journey without changing the team responsibilities they already hold.

04

Choose a course and keep your own pace

In Courses, inspect the programme before joining. Some offers are open to institution members, some require an invitation, and others require approval. Published versions provide a common structure while conversations and individual progression remain separate.

Leaving a course releases its place and preserves its learning history. Rejoining the same eligible group can restore that history, subject to admission and capacity. Choosing another group creates its own enrollment history.

Personal programmes depend on the institution’s learning policy. They are disabled by default in a new institution; ask the owner if the option is unavailable.

05

Support progress with the right context

Authorised staff can follow the institutional courses and groups within their scope. An individual progress report shows the learning evidence they are permitted to read. It does not open every private conversation.

Course estimates and review evidence help identify useful follow-up. Anonymous statistics suppress small groups; collective calibration requires enough independent, eligible observations within the same institution and programme version.

These signals are not grades, a diagnosis or an external certificate. An absent or suppressed value is not a zero.

06

Know what happens when an account changes

The account page shows your public identity, institution and roles. Separate local accounts keep their own conversations, settings and working folders. Switching accounts ends the previous agent session and its Tutor access.

Removing an account from this device and requesting erasure in an institution are separate actions. An institutional erasure concerns that organisation’s data and follows its documented processing and retention rules; it does not remove your local backups or other institutional memberships.

An institution’s last active owner must transfer ownership before requesting their own erasure. See Backups and updates before changing devices or restoring an identity.

Next steps

Keep going.

Source documentation

Before deploying or upgrading, read the release notes for the version you install. The repository provides the full contracts and operator details:

Found something unclear? Report a documentation issue.