Gameye vs Godot MCP
A side-by-side look at the Gameye and Godot MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
G
GameyeGaming · Local subprocess (stdio)Launch, inspect and stop multiplayer game server sessions on Gameye from any MCP client.53GoodAuth: api key requiredVerdict: choose Gameye for gaming 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?
GChoose Gameye when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
GAMEYE_API_TOKEN, GAMEYE_ENV, GAMEYE_API_URL, GAMEYE_TIMEOUT_MS. - You want tools like
gameye_context, gameye_launch_session, gameye_list_sessions.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | G Gameye | |
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 53/100 · Good | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | GAMEYE_API_TOKENGAMEYE_ENVGAMEYE_API_URLGAMEYE_TIMEOUT_MS | GODOT_PATHDEBUG |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 6,113 |
| Directory activity | 0 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 19 | 14 |
| Full listing | View Gameye | View Godot MCP |
Tools & capabilities
Gameye tools 19
gameye_contextShow the environment, host and server version this server targets, and the guardrail defaults (session TTL, `launched-by` label, token expiry)gameye_launch_sessionStart a containerized game server (billable). Default TTL and agent label applied; see [Guardrails](#guardrails)gameye_list_sessionsList running sessions (filterable; `all=true` for every status)gameye_describe_sessionGet session details, ports and playersgameye_stop_sessionStop one session by its exact IDgameye_player_joinRegister one or more players as joinedgameye_player_leaveRemove one or more players from a sessiongameye_get_locationsList locations that can host an image right nowgameye_list_regionsList the regions available to your organizationgameye_check_tagCheck whether an image tag is available in a regiongameye_list_applicationsList your applications with registry, resources, regions and portsgameye_list_registry_tagsList an application's tags in its upstream registry (paged)- +7 more on the listing page
Godot MCP tools 14
launch_editorLaunch Godot editor for a specific projectrun_projectRun the Godot project and capture outputget_debug_outputGet the current debug output and errorsstop_projectStop the currently running Godot projectget_godot_versionGet the installed Godot versionlist_projectsList Godot projects in a directoryget_project_infoRetrieve metadata about a Godot projectcreate_sceneCreate a new Godot scene fileadd_nodeAdd a node to an existing sceneload_spriteLoad a sprite into a Sprite2D nodeexport_mesh_libraryExport a scene as a MeshLibrary resourcesave_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.
Gameye
{
"mcpServers": {
"gameye": {
"command": "npx",
"args": [
"-y",
"gameye-mcp"
],
"env": {
"GAMEYE_API_TOKEN": "YOUR_GAMEYE_API_TOKEN_HERE",
"GAMEYE_ENV": "YOUR_GAMEYE_ENV_HERE",
"GAMEYE_API_URL": "YOUR_GAMEYE_API_URL_HERE",
"GAMEYE_TIMEOUT_MS": "YOUR_GAMEYE_TIMEOUT_MS_HERE"
}
}
}
}
Godot MCP
{
"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
Gameye is categorized under Gaming and uses a local stdio subprocess. Godot MCP belongs to Gaming and uses a local stdio subprocess. Pick Gameye for gaming 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.
Gameye is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 gameye and coding-solo-godot-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gameye has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Godot MCP has 67/100 (Great) with 6 views, 0 installs and 6,113 GitHub stars.