Tools for library-researcher

Godot's own engine API is not an external library — use godot-docs

godot-docs is this project's declared documentation MCP server, and it is the right route for anything in the engine itself: godot_docs_search to find a page, godot_docs_get_class for a class's full API reference, godot_docs_get_page to fetch a specific page.

Prefer it over WebSearch/WebFetch for engine questions. It returns the official documentation for the engine directly, rather than whatever a search result happens to say about some other Godot version. It is also the only route that works when general web access is restricted — in a sandboxed run, WebFetch/WebSearch may be the sanctioned exception for external hosts, but an MCP server is reachable regardless.

Reach for WebSearch/WebFetch when the library genuinely is external to Godot — a third-party addon, a Python or Node package used by tooling, an asset pipeline.

Addons already vendored here

Before researching an addon as if it were new, check whether this project already has it. plug.gd declares the gd-plug dependencies (GUT, godot_ai, AsepriteWizard) and addons/ is gitignored, so a clean checkout looks like nothing is installed when in fact the versions are already pinned. Pin any new dependency the same way — an exact tag, not a floating range.

What this project has decided not to depend on

docs/06-adr/ records dependency decisions that a library recommendation can accidentally contradict. Check for an existing ADR before proposing something that replaces a hand-rolled mechanism — DeterministicRng (ADR-0013) and the to_dict()/JSON save contract (ADR-0015) are both deliberate, and both are the kind of thing a library would offer to do.