Game engine runtime mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALLOWED_PROJECT_PATHS | Yes | The authorized game project folder path(s) that the sandboxed file operations are restricted to. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspeccionar_jerarquia_escenaB | Analiza la escena o mapa actual del motor (Unity/Godot) y devuelve el árbol de objetos, nodos y componentes asignados. |
| ejecutar_suite_pruebas_motorA | Ejecuta el Test Runner nativo del motor en modo Headless, filtrando el resultado para devolver solo fallos críticos y stacktraces limpios. |
| escribir_codigo_seguroA | Escribe o actualiza código dentro del Sandbox del proyecto verificando la estructura previa. |
| analizar_fugas_memoria_y_logsB | Lee los últimos logs de consola y los sintetiza automáticamente extraendo NullPointerExceptions, Warnings y métricas de rendimiento. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct concern: scene hierarchy inspection, test execution, safe code editing, and log/memory analysis. There is no meaningful overlap or risk of an agent selecting the wrong tool.
All tool names follow the same verb_noun pattern in lowercase snake_case: inspeccionar, ejecutar, escribir, analyzar. The naming is uniform and predictable.
Four tools is a reasonable size for a focused engine-runtime toolbox. Each tool appears to serve a distinct workflow, though the set could be slightly richer for a broad 'runtime' server.
The set covers scene inspection, test execution, code editing, and log analysis, but lacks direct runtime control and live state mutation features like play/pause, object property changes, or scene manipulation. These gaps limit what an agent can accomplish in an actual running game engine session.