Doyunha-Gopeak

★ 269

godot-mcp

★ 179

Doyunha-Gopeak vs godot-mcp

Q: Which is better, Doyunha-Gopeak or godot-mcp?

By GitHub stars, Doyunha-Gopeak has more community adoption, but the best choice depends on your specific use case.

Doyunha-Gopeak: GoPeak is an MCP (Model Context Protocol) server designed for Godot 4, enabling AI assistants to perform a complete development loop of editing, running, inspecting, and fixing within Godot projects. It provides tools for project control, scene/script editing, debugging, and runtime testing, facilitating AI-driven game development workflows.; godot-mcp: Godot-mcp empowers AI assistants with control over the Godot editor and running games, enabling deterministic playtesting and real-time state observation. It provides comprehensive tools for agents to set up scenarios, inject inputs, and verify changes without manual intervention.

TL;DR

Doyunha-GopeakDev Tooling · ★ 269

Listing Godot projects and displaying their information.

Read Doyunha-Gopeak full review →

godot-mcpDev Tooling · ★ 179

Automate UI layout testing across different resolutions and capture screenshots.

Read godot-mcp full review →

Side-by-Side Comparison

Field

Doyunha-Gopeak

godot-mcp

Features

Doyunha-Gopeak

01AI-driven Godot project control (find, launch, run, stop, debug output)

02Scene and script editing capabilities (create scenes, nodes, modify GDScript)

03Debugging support via logs, LSP diagnostics, DAP breakpoints, and runtime inspection

04Runtime testing with screenshots, live tree inspection, input injection, and method calls

05Extensible tool discovery and dynamic activation of capability groups

godot-mcp

01Deterministic playtesting with precise time stepping and input control.

02Live entity state as structured JSON for efficient game observation.

03Inject real game inputs with precise timing and comprehensive action types.

04Run GDScript within the running game for flexible test scenario setup.

05Extensive API with 21 tools and 86 actions for comprehensive control.

Use Cases

Doyunha-Gopeak

↳Listing Godot projects and displaying their information.

↳Automating scene and script creation, such as creating a player scene with a movement script.

↳Running projects, analyzing debug output, and fixing reported errors.

↳Discovering and activating specialized animation tools within Godot.

↳Inspecting live game states, capturing screenshots, and injecting runtime input for testing.

godot-mcp

↳Automate UI layout testing across different resolutions and capture screenshots.

↳Debug specific game states by stepping time and observing entity data.

↳Verify animation blending and input responsiveness with precise input injection.

↳Profile game performance to identify and diagnose frame rate spikes.

↳Automate in-editor asset creation and modification (e.g., animation authoring).

FAQ

What is the difference between Doyunha-Gopeak and godot-mcp?

Both Doyunha-Gopeak and godot-mcp are in the Dev Tooling category. Doyunha-Gopeak has 269 stars, while godot-mcp has 179 stars.

Which is better, Doyunha-Gopeak or godot-mcp?

The best choice depends on your use case. Choose Doyunha-Gopeak if Listing Godot projects and displaying their information., and godot-mcp if Automate UI layout testing across different resolutions and capture screenshots..

Is Doyunha-Gopeak free or open source?

Yes, Doyunha-Gopeak is open source on GitHub (MIT).

Is godot-mcp free or open source?

Yes, godot-mcp is open source on GitHub (MIT).

Cloud Infrastructure

Deploy on DigitalOcean

Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.

Claim $200 Free Credit

→

Alternatives to Doyunha-Gopeak →Alternatives to godot-mcp →Doyunha-Gopeak details →godot-mcp details →

TL;DR

Side-by-Side Comparison

Features

Use Cases

FAQ

Deploy on DigitalOcean

Related