M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionGodot MCP ServerMCP server for interfacing with the Godot game engineMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS61 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions11 / 2018 / 20
Maintenance14 / 2016 / 20
Documentation13 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • AI agents working with the Godot engine for development assistance
  • Developers who want to automate project launching and debug feedback loops
  • AI tools that need to dynamically create and modify scenes in Godot projects
  • 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
  • Developers not using the Godot engine
  • Users requiring remote or HTTP-based connections (only stdio transport)
  • Users without a need for Godot 4.4+ UID features
  • 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
  • Execute the Godot executable (to launch editor, run projects)
  • Read specified project directories to list projects and get information
  • Write files in the project directory to create scenes, add nodes, and save scenes
  • Read console output to capture debug information
  • 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
  • Running untrusted Godot projects may execute arbitrary code, posing security risks
  • Automatic modification of project files may lead to unintended changes; version control is recommended
  • Operations may fail if the Godot version or path is configured incorrectly
  • High volumes of operations may consume system resources, affecting performance
  • 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, Cline, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools140