Side-by-Side Model Context Protocol Comparison
Godot MCP Runtime vs Weppy Roblox MCP
In-depth architectural comparison of the Godot MCP Runtime and Weppy Roblox MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Godot MCP Runtime
Gaming · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Weppy Roblox MCP
Gaming · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Godot MCP Runtime if you need specialized Gaming tools running via a local process. Choose Weppy Roblox MCP if your workspace requires Gaming integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Godot MCP Runtime when:
- You need dedicated capabilities in the Gaming domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- You have access to required keys:
BRIDGE_PORT. - Primary tools included: launch_editor, run_project, attach_project.
Choose Weppy Roblox MCP when:
- You need dedicated capabilities in the Gaming domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: query_instances, mutate_instances, manage_properties.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Godot MCP Runtime Tools (39)
launch_editor
Open the Godot editor GUI for a project for the human user. Use only when the user explicitly asks to "open the editor"; for any agent-driven work, use the headless scene/node tools (add_node, set_node_properties, etc.) instead - the editor cannot be controlled programmatically. Returns plain-text confirmation after spawning the editor process. Errors if projectPath has no project.godot.
run_project
Spawn a Godot project as a child process with stdout/stderr captured. Required before take_screenshot, simulate_input, get_ui_elements, run_script, or get_debug_output. Set profiling: true at launch to enable the profiler tools. Use attach_project for one you launched yourself. Verifies MCP bridge readiness before returning success. Returns status with the assigned bridge port. Call stop_project when done. Errors if projectPath is not a Godot project or another session is already active.
attach_project
Inject the MCP bridge into a Godot process you launch yourself, then wait up to 20s for the bridge to start listening and up to 45s total once it has, so a large project's cold start is absorbed; a port that listens but answers no ping gives up sooner. Call BEFORE Godot launches - Godot reads autoloads only at process start, so a late call returns "bridge did not respond." Recommended pattern: kick off the Godot launch in parallel with this call so the wait absorbs startup. Prefer run_project unless MCP must not spawn Godot. Returns plain-text status with the resolved bridge port. Call detach_project or stop_project when done.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Godot MCP Runtime Configuration
Weppy Roblox MCP Configuration