Funplay Godot MCP Server

Funplay Godot MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. stdio bridge for the local Godot Editor MCP server from FunplayAI/funplay-godot-mcp.

What you get

The Most Advanced MCP Server for Godot Editor

• execute_code First — — The addon is optimized around one high-flexibility GDScript execution tool for rich editor/runtime orchestration, now with default-on safety checks for risky snippets
• Tool Exposure Control — — Toggle individual tools from the Godot dock without editing addon code or restarting the project
• Dock Dashboard — — See server state, tool exposure, runtime bridge heartbeat, release readiness, and project map actions inside Godot
• Bilingual Dock UI — — Switch Dock controls, tooltips, and operational status between English and Simplified Chinese with a persisted per-project preference
• Project Skills — — Generate project-local AI guidance files that capture the current endpoint, tool profile, project context, and recommended Funplay workflow
• Tool Catalog & Help — — Query grouped tool catalogs, capability gates, workflow coverage, and task-specific guidance from MCP

What the assistant can call

Once Funplay Godot MCP is connected, these are the calls the assistant has available:

• Category — Tools
• Scene — get_scene_info, get_scene_tree, list_scenes, open_scene, save_scene, save_scene_as, create_new_scene, instantiate_scene
• Nodes — get_node_info, find_nodes, select_node, create_node, duplicate_node, rename_node, reparent_node, remove_node, set_node_property, set_node_properties
• Scripts — create_script, list_scripts, edit_script, patch_script, open_script, validate_script, get_script_errors, request_script_reload; .NET projects also
• Files — read_file, write_file, search_files, list_files, file_exists, delete_file, move_file, copy_file
• Animation — create_animation_player, create_animation_clip, add_animation_track, list_animations, play_animation
• Camera — get_camera_info, set_camera_2d, set_camera_3d
• Materials — create_material, assign_material

Setting it up

The server ships on npm as funplay-godot-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration and credentials

You will need 2 environment variables: FUNPLAY_GODOT_MCP_URL, FUNPLAY_GODOT_MCP_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• This addon is Editor-only. It does not add runtime components to your exported game. - The MCP server starts on http://127.0.0.1:8765/ by default. If the same project already owns that port, the dock attaches to it; otherwise it falls back to another free local port. - Local MCP server settings are stored in user://funplay_mcp_settings.cfg. - The language selector localizes the Dock UI

Choosing this one

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Funplay Godot MCP's toolset — Category, Scene, Nodes and 5 more — is a fair guide to whether it matches your workflow. It is maintained by FunplayAI; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the funplay godot mcp mcp server does with a few real requests.