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.
git clone --depth 1 https://github.com/sterion66/godot-mcp-serverWrote 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/mcp/sterion66/godot-mcp-server/godot)<a href="https://agentmods.dev/mcp/sterion66/godot-mcp-server/godot"><img src="https://agentmods.dev/badge/mcp/sterion66/godot-mcp-server/godot/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/mcp/sterion66/godot-mcp-server/godot"><img src="https://agentmods.dev/badge/mcp/sterion66/godot-mcp-server/godot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
godot 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 9d 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.
What it actually says
{
"godot": {
"command": "uvx",
"args": [
"godot-mcp-server"
],
"env": {}
}
}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.
- 9d ago First seen · 9 lines scan A e835d6969f3f
godot is an MCP server published in the GitHub repository sterion66/godot-mcp-server (1 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-31.
Other mcp servers, from other repositories
godot-mcp
Agent-driven Godot playtesting: editor control, input injection, game-time stepping, live state. Runs locally from the @satelliteoflove/godot-mcp npm package. Needs 2 environment variables to run.
godot-mcp
MCP server for full Godot 4.x engine control with 165 tools for AI-driven game development. Runs locally from the @tugcantopaloglu/godot-mcp npm package.
gladekit-unity
MCP server "gladekit-unity" as configured in Glade-tool/glade-mcp. Runs gladekit_mcp with python.
glade-mcp
MCP server for Unity game development — connect Cursor, Claude Code, Windsurf, and other AI clients to your Unity Editor. Runs locally from the gladekit-mcp Python package.
unity-editor
MCP for Unity Server: A Unity package for Unity Editor integration via the Model Context Protocol (MCP). Runs locally from the mcpforunityserver Python package.
blender
Blender integration through the Model Context Protocol. Runs locally from the blender-mcp Python package.