Godot MCP vs Roblox Devforum MCP

A side-by-side look at the Godot MCP and Roblox Devforum MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Godot MCP logoGodot MCPGaming · Local subprocess (stdio)Agent-driven Godot playtesting: editor control, input injection, game-time stepping, live state.69GreatAuth: no auth requiredRoblox Devforum MCP logoRoblox Devforum MCPGaming · Local subprocess (stdio)MCP server that searches the Roblox DevForum and official creator docs so AI coding agents can debug Roblox games against real community and engine knowledge.64GoodAuth: no auth required

Verdict: choose Godot MCP for gaming work as a local process; choose Roblox Devforum MCP for gaming as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Godot MCP logoChoose Godot MCP when

  • You need dedicated capabilities in the Gaming domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like godot_scene, godot_node_read, godot_node_edit.
Explore Godot MCP

Roblox Devforum MCP logoChoose Roblox Devforum MCP when

  • You need dedicated capabilities in the Gaming domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like search_devforum, search_bugs, get_thread.
Explore Roblox Devforum MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGodot MCP logoGodot MCPRoblox Devforum MCP logoRoblox Devforum MCP
CategoryGamingGaming
Quality signal69/100 · Great64/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1794
Directory activity 3 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools2111

Tools & capabilities

Godot MCP tools 21

  • godot_sceneManage scenes in the editor: open a scene, save the open scene, or reload an open scene from disk after you edit its .tscn directly (so the editor picks up the change without a full restart). To create a new scene, write the .tscn file directly — header [gd_scene format=3] without a uid (the editor assigns one when it imports the file), then one [node name="X" type="Node2D"] block per node — and open it with this tool.
  • godot_node_readInspect scene nodes in the editor: read a node's effective properties (including class defaults a .tscn read cannot show), view the full scene tree as the editor sees it (including children inside instanced sub-scenes), and find nodes by name or type. Use it to discover node paths and verify the live state of the open scene before or after making changes. It cannot modify anything; to update properties or reparent a node, use godot_node_edit.
  • godot_node_editModify scene nodes in the editor: update a node's properties, or reparent it (the editor rewrites child paths and signal connections correctly; hand-editing .tscn for a reparent does not). Use it to change existing nodes in the open scene. To inspect properties, the scene tree, or search for nodes, use godot_node_read; to add or remove nodes, or attach scripts and connect signals, edit the .tscn file directly, then verify with godot_node_read's get_scene_tree.
  • godot_editor_readObserve the editor and running game: get editor state (open scene, play state, camera, viewport), read the current node selection, pull editor log messages (with an incremental cursor) and stack traces, and capture lossless PNG screenshots of the running game or an editor viewport. Reach for it to check what the editor sees before and after a change; screenshot_game needs a running game, while every other action works in the bare editor. It changes nothing - to select nodes, run/stop/restart, or move the 2D viewport use godot_editor_edit; errors from the running game (not the editor process) come via minimal-godot-mcp's get_console_output when that companion server is installed.
  • godot_editor_editDrive the editor: select a node, run or stop the project, restart the editor, rescan the filesystem to import assets written outside the editor, and center/zoom the 2D viewport. Use run with frozen=true as the deterministic-playtest entry point (game time holds at frame 0 until godot_game_time steps or thaws it). To test edited gameplay scripts just stop then run — the launched game loads .gd/.tscn fresh from disk; reserve restart for EDITOR-side staleness (edited @tool/addon code, a stale project.godot, or a cached .gdshader). For observation only (state, selection, logs, screenshots) use godot_editor_read instead; restart does not start a cold editor, so one must already be running.
  • godot_projectRead project-level data from the editor: name, path, Godot version, and main scene (get_info), plus project settings including input mappings (get_settings). After editing project.godot as a file, use check_stale to detect whether the editor is still running stale autoloads or input map from before the edit; restart via godot_editor_edit to reload. Use addon_status to diagnose addon/server version skew when commands misbehave or the connection drops; it also reports whether the running server build is stale relative to its source checkout. For scene contents or node properties, use godot_node_read instead.
  • godot_animation_readInspect animation data on AnimationPlayer nodes in the editor: list players in the scene, read a player's state and libraries, get an animation's tracks and properties, and read a track's keyframes. Reach for it to verify what the editor actually loaded, including after editing animation resources by hand. It changes and previews nothing; use godot_animation_edit to create, modify, or play animations.
  • godot_animation_editCreate and modify animations on an AnimationPlayer and preview them in the editor: create, delete, or update animations, add and remove tracks and keyframes, backfill RESET keys for existing tracks (create_reset_keys), and play, stop, or seek the editor's preview (playback controls the editor, not the running game). Pair each change with an immediate play or seek to check the result; this is the only way to verify animation feel without running the whole game. To inspect animation data without changing it, use godot_animation_read.
  • godot_tilemap_readInspect TileMapLayer data in the open scene: list layers, get layer and TileSet info, read used cells, a single cell, or a rectangular region, and convert between local positions and map coordinates. Use it whenever you need to know what tiles are placed where; cell data is stored base64-encoded in the .tscn, so reading the file is not an alternative. To place, erase, or clear tiles, use godot_tilemap_edit instead.
  • godot_tilemap_editModify TileMapLayer cells in the open scene: set a single cell, erase a cell, clear a whole layer, or set many cells in one batch. Use it to paint or remove tiles; cell data is stored base64-encoded in the .tscn, so editing the file is not an alternative, and set_cells_batch beats repeated set_cell calls for anything beyond a few tiles. To inspect layers, TileSets, or existing cells without changing anything, use godot_tilemap_read.
  • godot_gridmap_readInspect GridMap data in the open scene: list GridMap nodes, get map and MeshLibrary info, and read used cells, a single cell, or every cell using a given item. Use it whenever you need to know which mesh items occupy which 3D grid cells; cell data is stored base64-encoded in the .tscn, so reading the file is not an alternative. To place or clear cells, use godot_gridmap_edit instead.
  • godot_gridmap_editModify GridMap cells in the open scene: set a single cell to a MeshLibrary item with an orientation, clear a cell, clear the whole map, or set many cells in one batch. Use it to build or remove 3D grid content; cell data is stored base64-encoded in the .tscn, so editing the file is not an alternative, and set_cells_batch beats repeated set_cell calls for anything beyond a few cells. To inspect the map, its MeshLibrary, or existing cells without changing anything, use godot_gridmap_read.
  • +9 more on the listing page

Roblox Devforum MCP tools 11

  • search_devforumFull-text search across the Roblox Developer Forum. Use this first when a Roblox bug, error message, or engine behaviour needs community context: paste the literal error string (e.g. "502: API Services rejected request") or a symptom description. Results are re-ranked to favour solved and recent threads. Follow up with get_thread on the topic_id you want to read.
  • search_bugsSearch only the DevForum bug-report categories (engine, Studio, cloud services, mobile, website, Creator Hub, purchasing). Use this to answer "is this a known Roblox bug or is it my code?" — a hit means somebody reported the same symptom, with its category, last-activity date and whether a reply was marked as the solution. Roblox does not tag reports with a public triage state, so read the thread with get_thread to see whether staff actually answered.
  • get_threadRead a DevForum topic as Markdown: the original post plus the most useful replies, with the accepted answer hoisted to the top. Accepts a topic id or a full DevForum URL. Code blocks are preserved. Use get_replies to page through the rest.
  • get_repliesFetch a page of replies from a DevForum topic in post order. Use after get_thread when the answer is buried further down a long thread.
  • list_recentBrowse a category or tag without a search query. Use release-notes / announcements to check whether a recent Roblox update explains a regression, or scripting-support to see what is breaking for others right now.
  • list_categoriesList the DevForum category tree and the most-used tags. Call this when you are unsure which category or tag slug to pass to search_devforum, search_bugs, or list_recent.
  • search_creator_docsFind and read pages from Roblox's official creator documentation (create.roblox.com/docs). Call with `query` to list matching pages, then call again with `path` from a result to read that page in full. Use this for intended behaviour, limits and quotas, and guide-level explanations — pair it with search_devforum for what actually happens in production.
  • check_api_healthBatch-check Roblox APIs before you ship Luau that uses them. Pass entries like "Humanoid.MoveTo", "BodyVelocity", "Enum.Material.Neon", "task.wait" or "wait" and each is verified against the live API dump and the official docs: does it still exist, is it spelled with the right case, is it deprecated (with the official replacement where the docs give one), is it locked behind a security level normal scripts cannot use, and does it yield. Use this whenever you are about to write or review Roblox code — models often reproduce APIs that Roblox retired years ago.
  • get_engine_apiAuthoritative signature lookup from the live Roblox API dump: a class's properties, methods, events and callbacks with parameter types, security level, deprecation and thread safety. Use this to confirm a method exists, check whether it is deprecated or server-only, or find the right member name before writing Luau.
  • get_weekly_recapRead any Roblox Weekly Recap, current or historical. Roblox publishes one every Friday summarising what shipped that week: betas, engine updates, Marketplace and Studio changes. Use `week` to step back through the archive (0 = newest, 1 = the week before, …), `before` to jump to the recap covering a past date, or `list` to see the archive index. To find when a specific feature or regression landed, list the archive and read the recaps around that date.
  • get_whats_newA digest of recent Roblox platform changes: the official Weekly Recap, engine Release Notes, and Announcements. Use this when a game regressed for no obvious reason ("this worked last week"), when checking whether a Roblox update explains new behaviour, or when the user asks what is new on the platform. Returns the latest Weekly Recap body plus everything else published inside the time window.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Godot MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "godot-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "@satelliteoflove/godot-mcp"
      ]
    }
  }
}

Roblox Devforum MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "roblox-devforum-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "roblox-devforum-mcp"
      ]
    }
  }
}

Frequently asked questions

Godot MCP is categorized under Gaming and uses a local stdio subprocess. Roblox Devforum MCP belongs to Gaming and uses a local stdio subprocess. Pick Godot MCP for gaming work and Roblox Devforum MCP for gaming.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Godot MCP is listed as free. Auth: no auth required. Roblox Devforum MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add godot-mcp-2 and roblox-devforum-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Godot MCP has a quality signal of 69/100 (Great) with 3 views, 0 installs and 179 GitHub stars. Roblox Devforum MCP has 64/100 (Good) with 1 views, 0 installs and 4 GitHub stars.