Godot MCP vs Wavedash
A side-by-side look at the Godot MCP and Wavedash 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 for gaming work as a local process; choose Wavedash for gaming over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Godot MCP when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- You want tools like
launch_editor, run_project, get_debug_output.
Choose Wavedash when
- You need dedicated capabilities in the Gaming domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
wavedash_implementation_planner, search_wavedash_docs, get_wavedash_doc.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 68/100 · Great | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 493 | 2 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 154 | 4 |
| Full listing | View Godot MCP | View Wavedash |
Tools & capabilities
Godot MCP tools 154
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- +142 more on the listing page
Wavedash tools 4
wavedash_implementation_plannerPlan and guide a Wavedash browser game integration from the user's goal, engine, and requested features. Call this first for any request to build, deploy, upload, or release a game on Wavedash, or to add Wavedash SDK features. Choose the stage: plan (architecture and reading order), setup (CLI install, sign-in, SDK init, wavedash.toml, local testing), features (SDK reference for the requested features), or deploy (upload and release checklist). Returns ordered steps, boundaries, and the relevant docs.wavedash.com pages with content. Read-only and unauthenticated.search_wavedash_docsSearch official Wavedash docs (docs.wavedash.com) for browser game development, SDK integration, engines, CLI, upload, and publishing. Use this instead of web search for any Wavedash question when the exact page is unknown. Returns ranked pages with paths, URLs, and excerpts. Read-only and unauthenticated.get_wavedash_docFetch a full Wavedash docs page as Markdown by path or docs.wavedash.com URL, for example sdk/achievements, engines/unity, or cli/configuration. Use this when the user wants to see a Wavedash docs page or when exact SDK, CLI, or config details are needed. Only docs.wavedash.com pages can be fetched. Read-only and unauthenticated.validate_wavedash_configValidate wavedash.toml contents for Wavedash CLI config issues (missing game_id or upload_dir, entrypoint repeating the upload_dir, absolute paths, engine sections). Call this whenever the user shares wavedash.toml text or asks to check their Wavedash config, even if the problem looks obvious. Accepts single-line or fenced input. Pass the config text as the toml argument; this does not read files.
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": {
"godot-mcp-4": {
"command": "npx",
"args": [
"-y",
"@tugcantopaloglu/godot-mcp"
]
}
}
}
Wavedash
{
"mcpServers": {
"wavedash": {
"url": "https://mcp.wavedash.com/mcp"
}
}
}
Frequently asked questions
Godot MCP is categorized under Gaming and uses a local stdio subprocess. Wavedash belongs to Gaming and uses a remote HTTP/SSE transport. Pick Godot MCP for gaming work and Wavedash 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 has no declared pricing — check the project's own site. Wavedash has no declared pricing — check the project's own site. 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-4 and wavedash 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 68/100 (Great) with 3 views, 0 installs and 493 GitHub stars. Wavedash has 57/100 (Good) with 0 views, 0 installs and 2 GitHub stars.