1. Open Organization → Moodle and fill in Connect a Moodle site: a connection slug — lowercase letters, digits and hyphens, for example main-campus — and the Moodle URL of the site. HTTPS is required and the URL is validated against private address ranges, so a site that isn't publicly reachable is rejected here. 2. The panel generates two credentials and shows them only once: the license key, which identifies your install; the panel secret, used to sign every request between the plugin and the panel. Alongside them you'll also see this connection's connector URL — it isn't a secret, and you can look it up again on the connection's page whenever you need to. 3. Copy the values and paste them into the plugin: see the Moodle plugin. Holding the license key alone grants nothing: every request must also carry a valid signature computed with the secret, so the pair only works together.

Organization → Moodle → Rotate credentials immediately invalidates the current license key and secret and issues a new pair, shown once. Every owner and admin of the organization gets a security notification. Rotate when: the secret may have been exposed (sent by email, committed to a repository, seen by someone who has left); you're migrating the site to a different server or hosting provider; you've lost the values and need a working pair again. The connection stops working until you paste the new pair into the plugin, so plan for a couple of minutes of downtime for the assistants.

Connect your site — LMS MCP

Q: One organization, several Moodles

An organization can hold several Moodle connections — as many as your plan allows, and the page tells you how many slots are left. Each connection is 1:1 with an install (production and staging, or one per institution) and has its own credentials, its own keys, its own connector URL and its own usage.

Q: Verify the link

The plugin's Validate license button confirms the credentials and that the URL registered in the panel matches the site that's actually calling. Once verified, the panel caches your site's name, version and language from Moodle's own site-info call, and shows them on the Moodle page. If the check fails, Troubleshooting covers the usual causes.

One organization, several Moodles

An organization can hold several Moodle connections — as many as your plan allows, and the page tells you how many slots are left. Each connection is 1:1 with an install (production and staging, or one per institution) and has its own credentials, its own keys, its own connector URL and its own usage.

Register the site

Open Organization → Moodle and fill in Connect a Moodle site: a connection slug — lowercase letters, digits and hyphens, for example main-campus — and the Moodle URL of the site. HTTPS is required and the URL is validated against private address ranges, so a site that isn't publicly reachable is rejected here.
The panel generates two credentials and shows them only once:
- the license key, which identifies your install;
- the panel secret, used to sign every request between the plugin and the panel.
Alongside them you'll also see this connection's connector URL — it isn't a secret, and you can look it up again on the connection's page whenever you need to.
Copy the values and paste them into the plugin: see the Moodle plugin.

Holding the license key alone grants nothing: every request must also carry a valid signature computed with the secret, so the pair only works together.

Verify the link

The plugin's Validate license button confirms the credentials and that the URL registered in the panel matches the site that's actually calling. Once verified, the panel caches your site's name, version and language from Moodle's own site-info call, and shows them on the Moodle page.

If the check fails, Troubleshooting covers the usual causes.

Rotate credentials

Organization → Moodle → Rotate credentials immediately invalidates the current license key and secret and issues a new pair, shown once. Every owner and admin of the organization gets a security notification.

Rotate when:

the secret may have been exposed (sent by email, committed to a repository, seen by someone who has left);
you're migrating the site to a different server or hosting provider;
you've lost the values and need a working pair again.

The connection stops working until you paste the new pair into the plugin, so plan for a couple of minutes of downtime for the assistants.

Change the site URL

Changing the URL re-runs the same validation. If your Moodle moves to a new domain, update it here first, then re-validate from the plugin. Keys keep working: they're tied to the connection, not to the hostname.

Disconnect

Disconnecting removes the stored credentials and the encrypted Moodle tokens, and stops the MCP endpoint from resolving. Existing keys stop working immediately. The web-service tokens remain in your Moodle until you remove them there, so also revoke the users in the plugin if you're decommissioning the site.