A side-by-side look at the Godot MCP Bridge and Unity MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Godot MCP Bridge for gaming work as a local process; choose Unity 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?
Choose Godot MCP Bridge when
You need dedicated capabilities in the Gaming domain.
No tool names declared yet. Check the project README from the listing page.
Unity MCP tools
No tool names declared yet. Check the project README from 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.
Godot MCP Bridge is categorized under Gaming and uses a local stdio subprocess. Unity MCP belongs to Gaming and uses a local stdio subprocess. Pick Godot MCP Bridge for gaming work and Unity 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 Bridge has no declared pricing — check the project's own site. Unity MCP is listed as free. Auth: oauth 2.0. 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-bridge and ivanmurzak-unity-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Godot MCP Bridge has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 8 GitHub stars. Unity MCP has 56/100 (Good) with 4 views, 0 installs and 4,418 GitHub stars.