Moodle Developer Documentation MCP Server
Provides tools for searching, browsing, and retrieving Moodle developer documentation, including version-specific documentation and API structure.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Moodle Developer Documentation MCP Server Search for database API in Moodle 4.2"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Moodle Developer Documentation MCP Server
A Model Context Protocol (MCP) server that provides seamless access to Moodle developer documentation from moodledev.io. This server enables AI assistants and other MCP clients to search, browse, and retrieve Moodle development documentation with version-specific support.
Features
🔍 Search Documentation: Search across Moodle developer documentation with intelligent filtering
📚 Version Support: Access documentation for multiple Moodle versions (4.1, 4.2, 5.0, etc.)
🗂️ API Structure: Browse and explore Moodle's API documentation structure
📄 Page Fetching: Retrieve full content from specific documentation pages
⚡ Async Performance: Built with async/await for efficient concurrent operations
🔧 MCP Compatible: Works with any MCP-compatible client (Claude Desktop, etc.)
Related MCP server: ContextMCP
Installation
Prerequisites
Python 3.8 or higher
pip (Python package installer)
Install from PyPI
The easiest way to install the Moodle Developer Documentation MCP Server is via PyPI:
pip install moodle_dev_mcpFor Development or Specific Environments
If you're working in a virtual environment (recommended):
# Create a virtual environment
python -m venv moodle_mcp_env
# Activate the virtual environment
# On Windows:
moodle_mcp_env\Scripts\activate
# On macOS/Linux:
source moodle_mcp_env/bin/activate
# Install the package
pip install moodle_dev_mcpInstall with UV (Recommended for faster installs)
If you have uv installed:
uv pip install moodle_dev_mcpVerify Installation
After installation, verify that the server is properly installed:
python -c "import moodle_dev_mcp; print('Installation successful!')"Or test the server directly:
python -m moodle_dev_mcpConfiguration
Claude Desktop Integration
To use this MCP server with Claude Desktop, add the following configuration to your Claude Desktop config file:
Location of config file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Configuration:
{
"mcpServers": {
"moodle_dev_docs": {
"command": "python",
"args": ["-m", "moodle_dev_mcp"],
"env": {}
}
}
}If you installed in a virtual environment, use the full path to the Python executable:
{
"mcpServers": {
"moodle_dev_docs": {
"command": "/path/to/your/venv/bin/python",
"args": ["-m", "moodle_dev_mcp"],
"env": {}
}
}
}Other MCP Clients
For other MCP clients, use the following command to start the server:
python -m moodle_dev_mcpAvailable Tools
The server provides the following tools that can be used by MCP clients:
1. get_versions
Get a list of available Moodle versions in the developer documentation.
Parameters: None
Example usage:
Get available Moodle versions2. search_docs
Search Moodle developer documentation for specific topics or APIs.
Parameters:
query(required): Search query (e.g., "database API", "plugin development")version(optional): Specific Moodle version to searchlimit(optional): Maximum number of results (default: 10)
Example usage:
Search for "plugin development" in Moodle documentation
Search for "database API" in version 4.2 with limit 53. get_api_structure
Get the API documentation structure for a specific Moodle version.
Parameters:
version(optional): Moodle version (defaults to latest)
Example usage:
Get API structure for Moodle 4.2
Get latest API structure4. fetch_page
Fetch full content of a specific Moodle developer documentation page.
Parameters:
url(required): Full URL of the documentation page
Example usage:
Fetch content from https://moodledev.io/docs/apis/plugintypes/modUsage Examples
Once configured with your MCP client, you can use natural language to interact with the Moodle documentation:
Basic Searches
"Search for plugin development best practices"
"Find documentation about database APIs"
"Look up authentication methods in Moodle"
Version-Specific Queries
"Get API documentation for Moodle 4.2"
"Search for web services in version 5.0"
"Show me the plugin structure for the latest version"
Detailed Content Retrieval
"Fetch the complete plugin development guide"
"Get the full content of the database API documentation"
Development
Development Installation
For development, clone the repository and install in development mode:
git clone https://github.com/khairu-aqsara/moodle_dev_mcp.git
cd moodle_dev_mcp
# Install in development mode
pip install -e .
# Or with development dependencies
pip install -e ".[dev]"Dependencies
Python 3.8+
mcp: Model Context Protocol implementation
aiohttp: Async HTTP client for web requests
beautifulsoup4: HTML parsing and content extraction
Testing
Run tests with:
pytestTroubleshooting
Common Installation Issues
Permission Errors: Use
pip install --user moodle_dev_mcpif you encounter permission issuesPython Version: Ensure you're using Python 3.8 or higher:
python --versionVirtual Environment: Consider using a virtual environment to avoid conflicts
Runtime Issues
Network Connectivity: Ensure you have internet access to reach moodledev.io
Timeout Errors: The server includes built-in retry logic, but very slow connections may timeout
Rate Limiting: The server respects rate limits and includes appropriate delays
Debug Mode
Enable debug logging by setting the environment variable:
export PYTHONPATH=.
python -c "import logging; logging.basicConfig(level=logging.DEBUG)" -m moodle_dev_mcpContributing
Contributions are welcome! Please feel free to submit a Pull Request. For major changes, please open an issue first to discuss what you would like to change.
Development Setup
Fork the repository
Create a feature branch (
git checkout -b feature/amazing-feature)Make your changes
Run tests (
pytest)Commit your changes (
git commit -m 'Add amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
License
This project is licensed under the MIT License - see the LICENSE file for details.
Support
Issues: GitHub Issues
Discussions: GitHub Discussions
Email: wenkhairu@gmail.com
Acknowledgments
Built on the Model Context Protocol by Anthropic
Documentation sourced from Moodle Developer Resources
Thanks to the Moodle development community for comprehensive documentation
Note: This is an unofficial tool and is not affiliated with Moodle HQ. It's designed to make Moodle developer documentation more accessible through modern AI tools.
Available Tools
4 toolsfetch_pageB
Fetch full content of a specific Moodle developer documentation page
Inputs: url (required).
get_api_structureB
Get the API documentation structure for a specific Moodle version
Inputs: version.
get_versionsA
Get available Moodle versions in the developer documentation
Inputs: no named parameters.
search_docsA
Search Moodle developer documentation for specific topics or APIs
Inputs: query (required), version, limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a distinct, non-overlapping purpose: fetching pages, getting API structures, listing versions, and searching. No ambiguity in tool selection.
All tool names follow a consistent verb_noun pattern in snake_case (fetch_page, get_api_structure, get_versions, search_docs), making them predictable and easy to understand.
With 4 tools, the server is well-scoped for its purpose of browsing Moodle developer documentation. Each tool serves a necessary function without redundancy.
The tool set covers core documentation needs (retrieving pages, searching, version info, API structure). A minor gap is the lack of a tool to list all pages or browse categories, but this is compensable through search.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
An MCP server that gives your AI access to the source code and docs of all public github repos
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides version-pinned, deterministic documentation sourced from DevDocs.io to AI assistants (Claude, RooCode, Cline, Copilot etc.) and also via offline mode. Not via Scraping! But using the supported downloading option from devdocs.63 npm14MIT
- AlicenseNot gradedqualityAmaintenanceSelf-hosted MCP server that indexes documentation from various sources and makes it searchable by AI assistants via the Model Context Protocol and REST API.91Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA powerful Model Context Protocol (MCP) server implementation for seamless Google Docs API integration, enabling AI assistants to create, read, update, and manage Google Docs.14 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides a local MCP server for searching and retrieving documentation from 22+ open-source projects, enabling AI coding assistants to access up-to-date docs without network dependency.5 npm3MIT