Gopeak-godot-mcp
GoPeak is an MCP server for Godot Engine that exposes a large toolset (scene/project editing, runtime inspection, screenshots/input injection, and LSP/DAP-style debugging) to AI clients via the Model Context Protocol. It supports tool exposure profiles (compact/full/legacy), dynamic tool groups, and cursor-based pagination for tool listings.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security model is not documented. Defaults bind the bridge/visualizer host to 127.0.0.1, which reduces exposure, but the README does not describe authentication/authorization or TLS. The toolset includes powerful operations (running projects, editing scenes/resources, runtime inspection, and input injection), so you should treat it as high-privilege and restrict network access to localhost/trusted clients. Secret handling practices are not documented; avoid enabling debug logs in production unless you verify they don’t emit sensitive paths/tokens.
⚡ Reliability
Best When
You want an AI agent to work against a local Godot project with tight feedback loops (edit → run → inspect → debug) and can run the server locally (or on a trusted host).
Avoid When
You need strong multi-tenant security guarantees, or you must expose this service to untrusted clients over a network without additional controls.
Use Cases
- • AI-assisted Godot development: inspect/modify projects, scenes, and resources
- • Debug workflows: diagnostics, breakpoints, stepping, stack traces via DAP tools
- • Runtime testing: inspect live scene tree, set properties, take screenshots, inject input
- • GDScript development assistance via LSP-like tools (completions/hover/symbols)
- • Discovery/dynamic tooling: use tool.catalog and tool.groups to activate relevant tool subsets
Not For
- • Production-grade remote execution or unattended automation without sandboxing/permissions review
- • Use cases requiring a public, internet-facing authenticated HTTP API
- • Environments where running Godot (and any addons) is disallowed or cannot be controlled
Interface
Authentication
No user auth model is documented. Configuration is done via MCP client config and environment variables (e.g., GODOT_PATH, tool profile). If the server/bridge ports are reachable beyond localhost, you should assume no access control unless the implementation enforces it.
Pricing
Open-source (MIT) npm package; costs are primarily local compute (Godot + tooling) and any MCP client usage.
Agent Metadata
Known Gotchas
- ⚠ Tool exposure is profile-dependent (compact default). If tools are missing, you may need to switch GOPEAK_TOOL_PROFILE/MCP_TOOL_PROFILE or activate dynamic groups via tool.catalog/tool.groups.
- ⚠ Runtime tools require installing/enabling the runtime addon plugin in the Godot project.
- ⚠ Bridge/aux services use multiple ports; ensure the MCP client targets the intended local MCP transport and that required local ports are open.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Gopeak-godot-mcp.
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-03-30.