A
licenseNot graded
qualityD
maintenanceProvides AI assistants with access to the complete Godot Engine documentation, enabling developers to get answers about Godot classes, tutorials, and features directly in their chat interface.
74
MIT
Godot MCP Documentation Server
by banned104
Related Servers
Alternatives to Godot MCP Documentation Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables searching and reading Godot documentation as Markdown. Provides tools to search for terms and retrieve matching documentation pages through the Model Context Protocol.MIT
- AlicenseAqualityAmaintenanceServes the Godot Engine documentation to AI coding agents, grounding them with accurate APIs, exact signatures, and code examples to reduce hallucinations.5MIT
- FlicenseNot gradedqualityDmaintenanceBridges AI assistants with the Godot 4 editor, exposing tools to inspect scenes, create nodes, modify properties, capture screenshots, debug scripts, and manage project files via the Model Context Protocol.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and retrieve information from the official Godot game engine documentation. Provides tools to search documentation, get page content, and access detailed class information.25MIT
- AlicenseCqualityBmaintenanceModel Context Protocol server for Godot Engine providing 279 tools across 26 categories for AI assistants to read, inspect, and modify Godot projects via stdio transport.100988 npm40AGPL 3.0
TDQS
A3.9/5.0
Scored across 2 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count3/5
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.
Completeness3/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues