godot-dap-mcp-server
godot-dap-mcp-server is an MCP server (stdio-based) that bridges MCP clients to the Godot editor’s Debug Adapter Protocol (DAP) so AI agents can control and inspect a running Godot game/editor session for interactive runtime debugging (breakpoints, stepping, stack traces, variable inspection, expression evaluation, and scene launching).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
No authentication/authorization model is described. Debugging capabilities (breakpoints, expression evaluation, variable set being disabled) can be sensitive; exposure to untrusted networks should be avoided. MCP uses stdio and DAP uses TCP, but the README does not state encryption (TLS), network binding restrictions, or audit logging. Secret handling specifics (env vars, logging redaction) are not provided in the README.
⚡ Reliability
Best When
You are developing/debugging Godot projects locally (or in a controlled environment) and want an MCP client/agent to drive DAP interactions automatically.
Avoid When
You need secure remote access for untrusted users or require explicit, well-documented security controls (auth, network restrictions, audit logging) from the package itself.
Use Cases
- • AI-assisted interactive debugging of Godot gameplay logic at runtime
- • Automated investigation workflows: set breakpoints, reproduce, inspect locals/members/globals, and evaluate GDScript expressions
- • Agent-driven debugging sessions within an MCP client (e.g., Claude Code) using stdio transport
- • Launching and debugging specific scenes with configured debug options
Not For
- • Production-grade remote debugging exposed to untrusted networks without additional protections
- • High-scale multi-tenant debugging services (no sign of auth/rate limiting)
- • Use cases requiring strict compliance/auditing of debugging actions
Interface
Authentication
No authentication mechanisms are described in the provided README. Communication is stdio-based for MCP and TCP-based for DAP to the local Godot editor.
Pricing
Open-source project under MIT license; pricing not applicable.
Agent Metadata
Known Gotchas
- ⚠ Timeout protection exists, but retry/backoff guidance is not documented in the provided README.
- ⚠ Some features are disabled due to upstream Godot limitation (e.g., godot_set_variable).
- ⚠ Correct project path resolution (res:// to absolute) is important for reliable breakpoint/launch behavior.
- ⚠ DAP session state and interleaved events are complex; agents must respect ordering implied by the DAP session lifecycle.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for godot-dap-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.