Figwright vs Godot MCP

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

Figwright logoFigwrightArchitecture & Design · Local subprocess (stdio)Bidirectional Figma server over a local WebSocket relay: turn a selection into framework-aware code (reusing your components and tokens), or author frames, text, styles, variables, and whole screens back onto the canvas. 92 tools, any MCP client, no Dev Mode seat or paid tier.69GreatAuth: no auth requiredGodot MCP logoGodot MCPGaming · Local subprocess (stdio)A MCP server for interacting with the Godot game engine, providing tools for editing, running, debugging, and managing scenes in Godot projects.67GreatAuth: no auth required

Verdict: choose Figwright for architecture & design work as a local process; choose Godot 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?

Figwright logoChoose Figwright when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like Read, Write, Grounding.
Explore Figwright

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 have the keys it needs: GODOT_PATH, DEBUG.
  • You want tools like launch_editor, run_project, get_debug_output.
Explore Godot MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFigwright logoFigwrightGodot MCP logoGodot MCP
CategoryArchitecture & DesignGaming
Quality signal69/100 · Great67/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedGODOT_PATHDEBUG
Verified ownerCommunity listingCommunity listing
GitHub stars1,1556,293
Directory activity 6 views 0 installs 0 upvotes 10 views 0 installs 0 upvotes
Tools314

Tools & capabilities

Figwright tools 3

  • Readselection, document and node inspection, styles, variables, components, fonts, prototype reactions and flows, motion (animation) state, screenshots, original image-fill assets, PDF export, and video export of animated frames (MP4 / GIF / WebM); plus `list_files` / `use_file` for working across more…
  • Writecreate and edit frames, text, shapes (lines, polygons, stars, boolean operations, flattening), auto-layout, alignment and distribution, effects, images (as a new layer or into an existing layer's fill), styles, variables (including importing a team library's variables and styles, and switching a fr…
  • Grounding`get_design_context` for faithful, de-duplicated design context, and `component_map` / `token_map` / `icon_map`, which join Figma data to your codebase so codegen reuses what you already have; plus `design_diff`, which reports what changed in a design against a saved baseline so you update only the…

Godot MCP tools 14

  • launch_editorLaunch Godot editor for a specific project
  • run_projectRun the Godot project and capture output
  • get_debug_outputGet the current debug output and errors
  • stop_projectStop the currently running Godot project
  • get_godot_versionGet the installed Godot version
  • list_projectsList Godot projects in a directory
  • get_project_infoRetrieve metadata about a Godot project
  • create_sceneCreate a new Godot scene file
  • add_nodeAdd a node to an existing scene
  • load_spriteLoad a sprite into a Sprite2D node
  • export_mesh_libraryExport a scene as a MeshLibrary resource
  • save_sceneSave changes to a scene file
  • +2 more on the listing page

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.

Figwright

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "awdr74100-figwright": {
      "command": "npx",
      "args": [
        "-y",
        "@figwright/mcp@latest"
      ]
    }
  }
}

Godot MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "coding-solo-godot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@coding-solo/godot-mcp"
      ],
      "env": {
        "GODOT_PATH": "YOUR_GODOT_PATH_HERE",
        "DEBUG": "YOUR_DEBUG_HERE"
      }
    }
  }
}

Frequently asked questions

Figwright is categorized under Architecture & Design and uses a local stdio subprocess. Godot MCP belongs to Gaming and uses a local stdio subprocess. Pick Figwright for architecture & design work and Godot 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.

Figwright is listed as free. Auth: no auth required. Godot 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 awdr74100-figwright and coding-solo-godot-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Figwright has a quality signal of 69/100 (Great) with 6 views, 0 installs and 1,155 GitHub stars. Godot MCP has 67/100 (Great) with 10 views, 0 installs and 6,293 GitHub stars.