← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionGladeKit MCPConnect Unity and Godot editors to any MCP-compatible AI client.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS63 / 100 · C79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance13 / 2016 / 20
Documentation16 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Indie game developers and small teams looking to integrate AI into their Unity or Godot workflows.
  • Developers who want fast prototyping and asset import.
  • Tech-savvy developers who are comfortable configuring MCP servers.
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Large studios or teams that require strict asset curation may not want the AI-driven asset pipeline (can be disabled).
  • Environments requiring full offline operation or strict security may not suit the optional cloud features.
  • Godot Mono/C# projects or web export targets are not supported yet.
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Accesses local editor bridges via HTTP (ports 8765 for Unity, 8766 for Godot).
  • Reads and writes project files, including importing assets, creating GLADE.md, and reading scripts.
  • Optionally calls cloud services with OPENAI_API_KEY or GLADEKIT_API_KEY for semantic search, RAG, and cross-session memory.
  • Executes editor operations such as creating scenes, modifying objects, and running editor commands.
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • AI could perform unintended editor actions; use with version control and backups.
  • Asset pipeline allows only CC0-licensed assets, but users must verify license acceptance.
  • Cloud features (if enabled) send data to OpenAI or GladeKit servers, posing privacy risks.
  • The bridge is editor-only and does not affect exported games, but opens local network ports.
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Desktop, Claude Code, Cursor, Windsurf, VS Code, Unity AI Gateway, GitHub CopilotClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools80