AI Navigation
Teaches RQL Godot 2D/3D navigation — validated agent, region and link settings, a synchronous region Bake() with polygon counts, and NavigationPolygon outlines.
At a glance
What the agent can do with it
Adds no MCP tools: it contributes an RQL module with adapters for NavigationRegion3D, NavigationRegion2D, NavigationAgent3D, NavigationAgent2D, NavigationLink3D, NavigationLink2D, NavigationPolygon. That powers 3 capabilities the agent reaches through rql-query / rql-mutate. How RQL works →
- Agents, regions & links
Set validated agent settings (radius, distances, max speed, avoidance), region and link costs, and link endpoints on the 2D and 3D navigation nodes.
nodes | where name == "NavAgent" | set Radius = 0.75, MaxSpeed = 8, AvoidanceEnabled = true - Bake navigation
Bake a region’s NavigationMesh or NavigationPolygon synchronously and get its polygon count; add or clear NavigationPolygon outlines.
nodes | where name == "NavRegion" | call Bake() - Read navigation
List navigation regions, agents and links with their settings and baked polygon counts.
nodes | where $ is NavigationRegion3D | select name Enabled polygonCount NavigationMesh
Install
Requires the base plugin godot_mcp. Then build the project (godot-cli build <GodotProject>); the RQL module loads with the package — the agent sees it in rql-schema.
godot-cli install-extension com.IvanMurzak.Godot.MCP.Navigation <GodotProject>When to ask the AI for it
Ask for pathfinding setup in Godot — a baked nav region for the level, an agent on an enemy, or a link bridging two areas.
Example prompts
Copy-pasteable first requests. Start with one, verify it in the editor, then build up.
Add a NavigationRegion3D with a new NavigationMesh over the floor and bake it.Add a NavigationAgent3D to the Enemy with radius 0.75, max speed 8 and avoidance on.