Moodle Developer Documentation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_versionsA | Get available Moodle versions in the developer documentation |
| search_docsA | Search Moodle developer documentation for specific topics or APIs |
| get_api_structureB | Get the API documentation structure for a specific Moodle version |
| fetch_pageB | Fetch full content of a specific Moodle developer documentation page |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Available Moodle Versions | List of available Moodle versions in the developer documentation |
| API Categories | Available API categories in Moodle developer documentation |
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.