Ext Ops Panel
Open dashboard
Comparison

Plugged.in Proxy vs MoodleMCP

MoodleMCP is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑19.

Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). MoodleMCP is an MCP server published by moodlemcp.com. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacePlugged.in ProxyMoodleMCP
Docker MCP Catalog Listed
Version: sha256:b7c32590b270
Forks (GitHub): 30
Pulls (Docker Hub): 36 146
Stars (Docker Hub): 3
Stars (GitHub): 137
Not marked · First seen
Not listed
Official MCP Registry Not listed Removed on 2026-10-19
Version: 1.0.0
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Plugged.in Proxy vs MoodleMCP
FactPlugged.in ProxyMoodleMCPno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)137No figure on GitHub
Pulls (Docker Hub) (differs)36 146No figure on Docker Hub
Forks (GitHub) (differs)30No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/pluggedin-mcp-proxy)Remote server (moodlemcp.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)6Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/veriteknik/pluggedin-mcp-proxyNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of MoodleMCP

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • SLXD LMS MCP

    Manage your Moodle sites (courses, users, grades, reports) from an AI assistant.

    by slxd.app · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Canvas API MCP

    MCP server exposing the Canvas LMS REST API (1,116 endpoints) for AI assistants

    by JohannsenLum · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Moodle Student MCP

    Moodle MCP server for students. Read only access to courses, grades, due dates and announcements.

    by AnonymousOnyx22 · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • LearnWorlds

    All 94 LearnWorlds LMS API endpoints as safety-categorized MCP tools (read/write/destructive).

    by ohneben · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • LearnWorlds MCP by usefulapi

    Check LearnWorlds courses, learners, progress, grades and payments, and enroll or tag users.

    by usefulapi.io · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Mini Course Generator

    Build, publish and track interactive micro-courses, quizzes and learner analytics.

    by minicoursegenerator · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

Plugged.in Proxy

In its own words, on Docker MCP Catalog:

A unified MCP proxy that aggregates multiple MCP servers into one interface, enabling seamless tool discovery and management across all your AI interactions. Manage all your MCP servers from a single connection point with RAG capabilities and real-time notifications.

MoodleMCP

In its own words, on Official MCP Registry:

Connect your Moodle to AI assistants: courses, content, grading and reports from the chat.

How to run each

Plugged.in Proxy As a local MCP server: Docker image

Claude Code
claude mcp add --env "PLUGGEDIN_API_KEY=<YOUR_PLUGGEDIN_API_KEY>" --transport stdio pluggedin-mcp-proxy -- docker run -i --rm -e PLUGGEDIN_API_KEY mcp/pluggedin-mcp-proxy

Requires: PLUGGEDIN_API_KEY (secret)

MoodleMCP

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of MoodleMCP publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of MoodleMCP publish no settings it asks for, so we do not compare settings.

What it can do: Plugged.in Proxy · What it can do: MoodleMCP · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built