godot-docs-mcp
Serves the Godot Engine documentation to AI coding agents, grounding them with accurate APIs, exact signatures, and code examples to reduce hallucinations.
README
godot-docs-mcp
An MCP server that serves the Godot Engine documentation to AI coding agents.
Godot is under-represented in LLM training data relative to Unity and Unreal, so agents routinely hallucinate GDScript APIs, invent node names, and apply Godot 3.x idioms to 4.x projects. This server grounds them in the real docs: full-text search over the manual and tutorials, plus a structured class reference built from the engine's own API metadata.
Built on MCP specification revision 2026-07-28 via the official
mcp Python SDK v2, which also serves
every earlier protocol revision from the same server.
Status: in development. The server, its tools and resources, the command line, and the weekly workflow that publishes the index all work, and a prebuilt index for Godot 4.7 is published, so
syncinstalls one without a build. Not on PyPI yet — install from git, as below. Packaging as a Claude Code plugin, with skills, is a later phase.
How it works
The documentation is indexed offline into a single SQLite database, so lookups are fast and work without a network connection.
| Content | Source | Why |
|---|---|---|
| Manual, tutorials, getting started | godotengine/godot-docs .rst |
The authored prose |
| Class reference | godotengine/godot doc/classes/*.xml |
Structured and typed — the .rst class pages are generated from these, so the XML gives exact signatures rather than prose |
docs.godotengine.org sits behind a Cloudflare challenge that rejects non-browser clients,
so the rendered site is not used as a source. Everything comes from GitHub.
Getting started
Install the prebuilt index. It is one download of about 8 MB, and it only has to happen once per Godot version.
uvx --from git+https://github.com/mcintalmo/godot-docs-mcp godot-docs-mcp sync
uvx --from git+https://github.com/mcintalmo/godot-docs-mcp godot-docs-mcp status
Then point a client at it. For Claude Code:
claude mcp add godot-docs -- \
uvx --from git+https://github.com/mcintalmo/godot-docs-mcp godot-docs-mcp
No index published for the version you want, or working on the parsers? Build one from
source instead. That needs git and takes about a minute:
uvx --from git+https://github.com/mcintalmo/godot-docs-mcp godot-docs-mcp sync --rebuild
Ask something a model reliably gets wrong — "what's the correct 4.x signature for
move_and_slide?" — and the answer should come back from get_godot_class_member as
bool move_and_slide(), with no arguments. It took several in Godot 3.x, which is what most
training data remembers.
Commands
| Command | Purpose |
|---|---|
godot-docs-mcp |
Serve over stdio. This is what a client launches; serve is the default |
godot-docs-mcp sync |
Download a prebuilt index. --rebuild builds one from source instead |
godot-docs-mcp status |
What is indexed, what it was built from, and whether it has fallen behind. --json for a script |
godot-docs-mcp search "how do I make a character jump" |
Run a query through the same code the tools use, and print the ranking |
godot-docs-mcp package |
Write the release assets for the installed index. For the build workflow |
Every setting is also an environment variable, prefixed GODOT_DOCS_MCP_ — see
config.py for the full table.
Staying current
The documentation moves without warning, so two things track it independently.
A weekly workflow checks whether the upstream commits
have moved, and if they have, rebuilds the index, queries the whole corpus to confirm it
answers, and publishes it as a release asset. godot-docs-mcp sync is how that reaches you.
A running server checks once a day, in the background, whether a newer index has been
published. It never downloads one — an index that lags still answers correctly for the
version it was built from, and replacing it is your call. What it does instead is say so:
in godot://status, and as a one-line notice on search results. If the check cannot run,
the answer is "could not check", never "up to date".
Tools
Every tool is read-only, and every response is capped so that one call cannot crowd out the conversation it was meant to inform. A response that was cut says so, and names the call that returns the rest.
| Tool | Purpose |
|---|---|
search_godot_docs |
Ranked search across the manual, tutorials, and class reference. Questions in plain words work |
fetch_godot_doc |
A page, or a single section of one |
get_godot_class |
Inheritance chain plus a signature map for a class — no prose, so a 300 KB class entry stays answerable |
get_godot_class_member |
Exact signature and full description for one member |
search_godot_code_examples |
GDScript and C# snippets, with the page and heading they came from |
Resources
| URI | Content |
|---|---|
godot://status |
Indexed version, counts, and the upstream commits it was built from |
godot://index |
A map of the corpus: what it holds, how it is addressed, which tool to call |
godot://doc/{path}, godot://doc/{path}#{anchor} |
A page, or one section of it |
godot://class/{name}, godot://class/{name}#{member} |
A class, or one member of it |
The 515 pages and 1,078 classes are deliberately not enumerated in resources/list.
The templates are the URIs every tool already returns, so a search hit can be followed by
the host without a further tool call.
Development
Requires uv.
uv sync --dev
uv run pre-commit install
| Command | Purpose |
|---|---|
uv run pytest |
Unit suite (hermetic — no network) |
uv run pytest -m slow |
Integration tests against a real index |
uv run ruff check --fix && uv run ruff format |
Lint and format |
uv run ty check |
Type check |
uv run pre-commit run --all-files |
Everything the CI lint job runs |
See CLAUDE.md for the architecture and contribution conventions.
License
MIT. The Godot documentation itself is licensed CC BY 4.0 by Juan Linietsky, Ariel Manzur and the Godot community; this project redistributes an indexed form of it and does not alter that license.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。