MoodlIA
ENES
Get help

MoodlIA Sync MCP

Coordinates reviewed course-content plans between different Moodle sites.

View the coordinator on GitHubSee installation and first-use stepsAsk about this project

Cross-site MCP coordinatorDeveloper preview

An educator planning a course with lesson notes and a laptop in a bright learning space
AI that supports the way you already teach

Here for one clear job.

A separate MCP server for one-way, no-backup synchronization across Moodle 4.5 and later sites. Each endpoint may use MoodlIA, Moodle Core services, or both, while policy and exact plan approval remain outside the model.

01

What it helps with

  • Uses the same adaptive planning and recovery engine as the CLI
  • Keeps Moodle tokens and binary assets outside MCP arguments and results
  • Supports durable status, cancellation, reconciliation, conflicts, verification, and history

02

A good fit for

  • Administrators coordinating selected content between separate Moodle sites
  • MCP clients that need a policy-bound cross-site workflow
  • Mixed Moodle versions or sites where only one endpoint has MoodlIA

03

What you need

  • Node.js 22.5 or later
  • Explicit profile, course/category, direction, and effect allowlists
  • Separate limited REST credentials for every Moodle endpoint

How installation and use work.

This is a coordinator, not another Moodle plugin. The MCP endpoint inside the MoodlIA plugin continues to operate one Moodle site.

Set it up once

  1. Ask an administrator to define the authorized site profiles and pair policy.
  2. Run the coordinator locally over stdio, or place its HTTP listener behind authenticated TLS.
  3. Keep Moodle tokens in environment variables and never in MCP tool arguments.

Try one small thing

  1. Discover both endpoints and create a read-only synchronization plan.
  2. Review every action, gap, conflict, provider, effect, and byte estimate.
  3. Approve the exact plan digest outside the AI client, then verify the completed job by live readback.
Get help to start this tool

CONCRETE STEPS

Run the MoodlIA Sync MCP coordinator

Use this developer preview only after an administrator has defined the exact site, course, category, direction, and effect policy.

  1. Review the coordinator

    Read its security, profile, policy, and recovery model before connecting Moodle credentials.

    Open MoodlIA Sync MCP on GitHub

  2. Choose a protected transport

    Prefer local stdio. For remote MCP, use a strong Bearer credential, an allowed-host list, and authenticated TLS in front of the loopback service.

  3. Create a read-only plan

    Discover both Moodle sites and inspect the immutable plan, unsupported changes, conflicts, selected providers, and estimated transfer.

  4. Approve and verify

    Approve the exact digest outside the MCP model, monitor the durable job, and finish with a fresh Moodle readback.

01MoodlIA Moodle Plugin02MoodlIA CLI03Moodle Core CLI04MoodlIA Skills
Explore all plan with ai projects

Want help with MoodlIA Sync MCP?

Tell us what you are trying to achieve. We can help you choose, start, configure, or troubleshoot the right MoodlIA project.

Write to contact@moodlia.com