Requirements

Moodle version

The plugin requires Moodle 4.2 or later and is tested up to Moodle 5.1. Older sites can't install it: the plugin relies on web-service APIs that landed in 4.2.

Your Moodle must be reachable over HTTPS

The panel and the MCP server call your site directly, so it needs a public HTTPS URL with a valid certificate. Sites on localhost, on a private network (10.x, 192.168.x, …) or behind a VPN are rejected — the URL is validated against private address ranges when you connect.

A staging site works fine as long as it is publicly reachable.

Web services must be enabled

Under Site administration → Advanced features, enable web services, and under Manage protocols enable the REST protocol. The plugin creates its own role-scoped services; it does not reuse or modify any service you already have.

Who can set this up

• In Moodle — a user with site administrator rights, to install the plugin and provision users.
• In the panel — an organization owner or admin, to connect the site, mint keys and manage billing. Members can use the chat but can't change the connection.

An account with an active subscription

MoodleMCP is a subscription service. New organizations start on a 30-day trial that doesn't ask for a card; after that an active subscription is required to keep using the connection. See Plan & billing.

What you don't need

• No changes to your students' or teachers' accounts — access is provisioned per user, when you choose to.
• No inbound firewall rules: your Moodle is called over its normal public HTTPS endpoint, and the plugin only makes outbound requests to the panel.
• No server access — everything happens through the Moodle admin UI.