Funplay Cocos MCP vs Gopeak

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

Funplay Cocos MCP logoFunplay Cocos MCPGaming · Local subprocess (stdio)stdio bridge for the local Cocos Creator Editor MCP server from FunplayAI/funplay-cocos-mcp.52GoodAuth: no auth requiredGopeak logoGopeakGaming · Local subprocess (stdio)GoPeak — The most comprehensive MCP server for Godot Engine. 95+ tools, LSP, DAP, screenshots.67GreatAuth: no auth required

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

Which MCP server should you choose?

Funplay Cocos MCP logoChoose Funplay Cocos 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.
Explore Funplay Cocos MCP

Gopeak logoChoose Gopeak 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, GOPEAK_TOOL_PROFILE, MCP_TOOL_PROFILE.
  • You want tools like tool-catalog, project-list, project-info.
Explore Gopeak

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFunplay Cocos MCP logoFunplay Cocos MCPGopeak logoGopeak
CategoryGamingGaming
Quality signal52/100 · Good67/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedGODOT_PATHGOPEAK_TOOL_PROFILEMCP_TOOL_PROFILE
Verified ownerCommunity listingCommunity listing
GitHub stars350269
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listed33

Tools & capabilities

Funplay Cocos MCP tools

No tool names declared yet. Check the project README from the listing page.

Gopeak tools 33

  • tool-catalog[compact alias of tool_catalog] Discover available tools including hidden legacy tools. Use query to search by capability keywords. Results include group categorization (core/dynamic). Matching dynamic groups are auto-activated and become available immediately. Core groups (always visible): core_meta, core_project, core_editor, core_scene, core_script, core_class, core_signal, core_resource, core_export, core_runtime, core_visualizer, core_diagnostics. Dynamic groups (on-demand): scene_advanced, uid, import_export, autoload, signal, runtime, resource, animation, plugin, input, tilemap, audio, navigation, theme_ui, asset_store, testing, dx_tools, intent_tracking, class_advanced, lsp, dap, version_gate.
  • project-list[compact alias of list_projects] Scans a directory for Godot projects (folders containing project.godot). Use to discover projects before using other tools. Returns array of {path, name}.
  • project-info[compact alias of get_project_info] Returns metadata about a Godot project including name, version, main scene, autoloads, and directory structure. Use to understand project before modifying. Requires valid project.godot.
  • project-search[compact alias of search_project] Searches for text or regex patterns across project files. Use to find function usages, variable references, or TODOs. Returns file paths and line numbers.
  • project-setting-get[compact alias of get_project_setting] Reads a value from project.godot settings. Use to check game name, window size, physics settings, etc.
  • project-setting-set[compact alias of set_project_setting] Writes a value to project.godot settings. Use to configure game name, window size, physics, etc.
  • editor-launch[compact alias of launch_editor] Opens the Godot editor GUI for a project. Use when visual inspection or manual editing of scenes/scripts is needed. Opens a new window on the host system. Requires: project directory with project.godot file.
  • editor-run[compact alias of run_project] Launches a Godot project in a new window and captures output. Use to test gameplay or verify script behavior. Runs until stop_project is called. Use get_debug_output to retrieve logs.
  • editor-stop[compact alias of stop_project] Terminates the currently running Godot project process. Use to stop a project started with run_project. No effect if no project is running.
  • editor-debug-output[compact alias of get_debug_output] Retrieves console output and errors from the currently running Godot project. Use after run_project to check logs, errors, and print statements. Returns empty if no project is running.
  • editor-status[compact alias of get_editor_status] Returns the connection status of the Godot Editor Plugin bridge. Use to check if the editor is connected before using scene/resource tools that require the editor plugin.
  • editor-version[compact alias of get_godot_version] Returns the installed Godot engine version string. Use to check compatibility (e.g., Godot 4.4+ features like UID). Returns version like "4.3.stable" or "4.4.dev".
  • +21 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.

Funplay Cocos MCP

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

Gopeak

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "gopeak": {
      "command": "npx",
      "args": [
        "-y",
        "gopeak"
      ],
      "env": {
        "GODOT_PATH": "YOUR_GODOT_PATH_HERE",
        "GOPEAK_TOOL_PROFILE": "YOUR_GOPEAK_TOOL_PROFILE_HERE",
        "MCP_TOOL_PROFILE": "YOUR_MCP_TOOL_PROFILE_HERE"
      }
    }
  }
}

Frequently asked questions

Funplay Cocos MCP is categorized under Gaming and uses a local stdio subprocess. Gopeak belongs to Gaming and uses a local stdio subprocess. Pick Funplay Cocos MCP for gaming work and Gopeak 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.

Funplay Cocos MCP is listed as free. Auth: no auth required. Gopeak 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 funplay-cocos-mcp and gopeak as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Funplay Cocos MCP has a quality signal of 52/100 (Good) with 1 views, 0 installs and 350 GitHub stars. Gopeak has 67/100 (Great) with 1 views, 0 installs and 269 GitHub stars.