FAQ

Common questions about MCP-Moodle.

Is it free?

Yes. The MCP server is MIT-licensed and the Moodle plugin is GPLv3, so the whole project is open source and free to use, modify and self-host.

Can it create Moodle plugins?

No. It builds content inside Moodle (courses, activities, quizzes, users, grades) through Moodle's web services. It cannot write or install plugin code, activity types, blocks or themes. The single plugin it relies on, local_mcpbridge, is installed once by an admin and is what gives the AI its activity-creation tools.

Do I need to write code?

No. Install the plugin, run the server, and chat. The AI turns your plain-English requests into the right tool calls for you.

Which AI clients work? Only Claude?

Any MCP client — not only Claude. MCP is an open protocol, so Claude Desktop, Claude Code, Gemini CLI, ChatGPT desktop (developer mode), Cursor, Windsurf, VS Code Copilot agent mode, Cline and LM Studio all work with the same command and env vars. See the client setup page for a Gemini CLI example. Tool-use quality depends on the model: stronger models chain the 88 tools more reliably than small local ones.

Does it work on hosted or managed Moodle?

It runs on any Moodle 4.2 or newer that you can administer, self-hosted or institutional. Managed clouds that block custom plugins (for example the MoodleCloud free tier) cannot do activity creation, though read-only tools may still work.

Is it safe for my institution's Moodle?

Yes. The AI authenticates with a web service token, never a password, and can only do what that token's user is allowed to do. Create a dedicated, least-privilege service account and scope it to exactly the capabilities you want to expose.

Can it delete or change things?

Only if you opt in. Set MOODLE_ALLOW_WRITE=true and give the token's user the capability. By default the server registers read-only tools, so writes cannot happen by accident.

What data leaves my server?

The server talks only to your Moodle over HTTPS using the token. Your AI client sees the tool results you ask for. Nothing else is sent anywhere.

How does it handle logins like SSO or LDAP?

Tokens are a separate channel, independent of how your users sign in. SSO/SAML, LDAP, Google or Microsoft OAuth, CAS or manual accounts all work identically.

How long does setup take?

A few minutes: install the plugin, enable web services, create a token, run the server, and connect your client. Follow the five Setup steps in order.

Where do I get help?

Start with Troubleshooting. If you're still stuck, open a GitHub issue.