What it covers

This page lists, for each part of a Godot project, the tools that make and change it and the tools that read it back or watch it in a running game. Every tool is in the full profile; Profiles and answers says which smaller profile holds it.

Two words in the table stand for a group of tools:

• Edit is a call_method operation in scene.batch.apply, editor.scene.edit or resource.batch.apply, or in the operations of scene.create and resource.create. It calls one method of a fixed table, such as add_track on an Animation; the editor bridge reference lists every method each class takes.
• Read is a call of scene.read, resource.read or, for the scene your editor holds, editor.scene.read, which asks the engine for what only it knows, such as the painted cells of a tile map.

Area	Make and change	Read back, run and observe
Animation	Edit AnimationPlayer, AnimationLibrary and Animation: add_animation, add_track, track_insert_key, set_loop_mode; SpriteFrames for frame animations	Read get_animation_list, track_get_key_count, track_get_key_value; in a game, runtime.signals.get and runtime.wait
AnimationTree	Edit AnimationNodeStateMachine (add_node, add_transition), AnimationNodeBlendTree (connect_node) and the blend spaces (add_blend_point)	Read get_node_list, get_transition_count, get_blend_point_count
Physics	scene.recipe.apply with body-2d or body-3d: a character, rigid, static or area body with its shape; set_subresource for any shape; TileSet physics layers	scene.tree.get; in a game, runtime.nodes.find near a point, runtime.properties.get, runtime.sample, runtime.time_scale.set
3D	scene.recipe.apply with body-3d, light-3d (sun, lamp, sky, camera) or gridmap-3d; edit GridMap (set_cell_item) and MeshLibrary (create_item)	Read get_used_cells, a mesh's get_aabb, a Skeleton3D's bones; editor.camera.get, editor.camera.set, editor.screenshot.capture of a 3D viewport
Particles	scene.recipe.apply with particles-2d and a preset: fire, smoke, sparks, rain, snow or explosion; set_subresource for a ParticleProcessMaterial	In a game, runtime.screenshot.capture, runtime.recording.capture, runtime.image.compare
Navigation	scene.recipe.apply with navigation-2d; edit NavigationPolygon (add_outline) and bake with the regions' bake_navigation_polygon and bake_navigation_mesh	Read get_polygon_count, get_vertices; in a game, runtime.navigation.path.get and runtime.node.move along a path
Audio	asset.put and project.import.run for the sound, scene.recipe.apply with audio-2d, resource.batch.apply on the bus layout (default_bus_layout.tres) for its buses; project.settings.patch chooses another layout file	asset.status, resource.tree.get on the bus layout; in a game, runtime.properties.get on the player
Shaders	file.create for a .gdshader; scene.recipe.apply with shader-2d for a ShaderMaterial and its uniforms; edit VisualShader (add_node, connect_nodes)	shader.check for compile errors and uniforms; read get_shader_uniform_list
Themes	resource.create or resource.batch.apply editing a Theme (set_color, set_font_size, set_constant, set_stylebox), as the theme recipe does; scene.recipe.apply with hud; edit Control anchors	Read get_color, get_type_list; in a game, runtime.ui.get and runtime.ui.press
TileMap	Edit TileSet and TileSetAtlasSource (add_source, create_tile, terrains) and TileMapLayer (set_cell, erase_cell, set_cells_terrain_connect)	Read get_used_cells, get_cell_source_id, get_cell_atlas_coords
Runtime control	project.run.start and project.run.stop; input.action.send, input.key.send, input.mouse.send, input.sequence.send, input.replay	runtime.tree.get, runtime.properties.get, runtime.properties.set, runtime.wait, runtime.ui.get, runtime.screenshot.capture; test.scenario.run for a whole scenario

Recipes

scene.recipe.apply adds a common setup to a scene by name, with its parameters, and answers every value it used. It turns the recipe into one batch of the operations above, journaled and checked against the scene's SHA-256, or, when your editor holds the scene, into one undoable action. Ten recipes go into scenes: body-2d, body-3d, light-3d, particles-2d, navigation-2d, audio-2d, shader-2d, hud, gridmap-3d and joystick, the last on Godot 4.7.1, where the VirtualJoystick class exists. The theme recipe makes a resource and goes to resource.create.

{
  "path": "scenes/fire.tscn",
  "expectedSha256": "<the scene's current SHA-256>",
  "recipe": { "particles-2d": { "preset": "smoke" } },
  "idempotencyId": "<a new unique id>"
}

An agent finds the recipes without this page: each one is also an MCP prompt, godot-mcp.recipe.<name>, in the editor and full profiles, with the recipe's parameters, a call and the operations it becomes. A prompt takes no tool slot. The recipes reference shows every recipe's call, its operations and its parameters.

Everything else

The tools reference lists all 130 tools with their profiles. A part of Godot with no edit method or recipe here is still reachable: a batch sets a node's stored properties with set_property and embeds resources in it with set_subresource, and, once you start the server with --allow-scripts, script.run, editor.script.run and runtime.script.run run GDScript an agent writes.