Godot MCP Documentation 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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_documentation_treeA | Get a tree-style overview of the documentation folder. Returns: String containing a directory tree representation of the documentation. Usage Examples: - get_documentation_overview() -> Full docs tree from root Note: Files are exposed via get_documentation_resource(file_path: str) resource. |
| get_documentation_fileA | Get the content of a specific documentation file. Args: file_path: Path to the documentation file relative to the docs directory (e.g., "classes/class_camera2d.md"). Returns: The content of the requested documentation file, or an error message if not found. Usage Example: - get_documentation_file("classes/class_camera2d.md") -> Content of class_camera2d.md |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_documentation_file retrieves specific file content, while get_documentation_tree provides a structural overview. There is no overlap in functionality, making it impossible for an agent to confuse them.
Both tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming. The naming is perfectly predictable across the tool set, with no deviations in style or convention.
With only 2 tools, the server feels thin for a documentation server that might benefit from additional operations like search, navigation, or metadata retrieval. While the tools cover basic reading and browsing, the count is borderline minimal for the apparent scope.
The server provides core read operations (get file, get tree) but lacks obvious enhancements like search functionality, content filtering, or version-specific documentation access. The surface is functional but incomplete for comprehensive documentation interaction, leaving notable gaps in typical documentation workflows.