Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add yurineko73/Godot-MCP-Native --skill gdmcpgit clone --depth 1 https://github.com/yurineko73/Godot-MCP-NativeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/yurineko73/godot-mcp-native/gdmcp)<a href="https://agentmods.dev/skills/yurineko73/godot-mcp-native/gdmcp"><img src="https://agentmods.dev/badge/skills/yurineko73/godot-mcp-native/gdmcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/yurineko73/godot-mcp-native/gdmcp"><img src="https://agentmods.dev/badge/skills/yurineko73/godot-mcp-native/gdmcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00034 | $0.01110 |
| Opus 5 | $0.00017 | $0.00555 |
| Sonnet 5 | $0.00007 | $0.00222 |
| Haiku 4.5 | $0.00003 | $0.00111 |
Grade A, and why
gdmcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gdmcp
Use gdmcp from the shell for operations that require the running Godot editor.
By default, invoke the project-local CLI from the project root at .\.gdmcp\bin\gdmcp.exe in PowerShell; the gdmcp command in the examples below is shorthand for this path. Use a PATH-installed gdmcp only as an explicit fallback when the local executable is unavailable.
Project directory and configuration discovery
Run the CLI from the Godot project root when possible. The CLI uses the
process working directory to discover project.godot, then resolves the
project's Godot user://mcp_settings.cfg so a persisted HTTP http_port is
used automatically. The CLI executable directory (for example
.gdmcp/bin) is not used as the project directory.
When the current directory is not the project root, provide the project and, if necessary, Godot's custom user-data root explicitly:
gdmcp --project-path <project-root> --godot-user-data-dir <godot-user-data-root> --json doctor
Equivalent environment variables are GODOT_MCP_PROJECT_PATH and
GODOT_USER_DATA_DIR. URL precedence remains: explicit --url,
GODOT_MCP_URL, the CLI config file, the discovered Godot MCP settings, then
the built-in http://127.0.0.1:9080 fallback. Stdio MCP settings do not
produce an HTTP endpoint and therefore use the normal fallback chain.
Start with:
gdmcp --json doctor
gdmcp --json editor state
Prefer narrow domain commands for common operations:
gdmcp --json scenes current
gdmcp --json scenes list --limit 20
gdmcp --json scenes tree --depth 4
gdmcp --json nodes list --limit 20
gdmcp --json nodes get /root/Main/Player --fields position,visible
gdmcp --json nodes properties set /root/Main/Player --property speed --value 300
gdmcp --json scripts list --limit 20
gdmcp --json scripts read res://player.gd --lines 1:200
gdmcp --json scripts create res://new_script.gd --script-type GDScript
gdmcp --json resources list --limit 20
gdmcp --json resources get res://player.tres --fields resource_path
gdmcp --json project settings --filter display/
gdmcp --json debug logs --limit 50
gdmcp --json runtime tree --depth 4
gdmcp --json runtime nodes get /root/Main/Player
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 104 lines · 34 tokens per session scan A 447277794d1b
gdmcp is a skill published in the GitHub repository yurineko73/Godot-MCP-Native (771 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,110 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
minecraft-debug-mcp
Operate and debug the live Minecraft bot through its built-in MCP REPL server. Use when work requires starting the bot with pnpm dev, connecting to the local MCP endpoint, inspecting cognitive state/logs/history, injecting synthetic chat/events, or running targeted REPL code against the running brain during…
graphics-api-hooking
Analyze Direct3D/DXGI, OpenGL, and Vulkan rendering, presentation, composition, and capture evidence. Use to distinguish API samples, PresentMon event metrics, Tracy instrumentation, compatibility translation, frame images, and validation diagnostics; review swap chains, overlays, resource lifetime, and…
console-get-logs
Retrieve Unity Editor logs from the MCP plugin's LogCollector, optionally filtered by log type or time window. Useful for debugging and monitoring Editor activity.
editor-application-get-state
Return the current state of UnityEditor.EditorApplication — playmode, paused state, compilation state, and related flags.
console-clear-logs
Clear the MCP log cache (used by 'console-get-logs') and the Unity Editor Console window. Useful for isolating logs to a specific action by clearing the slate first.
profiler-start
Enable Unity's runtime profiler and open the Profiler window. Idempotent: calling when already enabled returns the current enabled state without error.