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.

DimensionUnity API Documentation MCP ServerAccurate Unity API documentation for AI agents, with no hallucinated signaturesMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS59 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions11 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Teams developing Unity projects with Claude Code, Cursor, or Windsurf
  • Developers who want to avoid AI-invented Unity API signatures
  • Projects on Unity 6, Unity 2023, or Unity 2022 LTS
  • AI-assisted workflows that want to reduce source-file reads, saving context and tokens
  • 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
  • Users who need third-party assets like DOTween, VContainer, or Newtonsoft.Json (not indexed)
  • Developers using Unreal Engine or non-Unity engines
  • Environments with Python below 3.10
  • Anyone needing official Unity support (this is an independent third-party project)
  • 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
  • Read access to local MCP configuration files
  • Network access on first run to download the database (~20-30 MB)
  • Read/write access to ~/.unity-api-mcp/ to cache databases
  • Optional UNITY_PROJECT_PATH reads ProjectSettings/ProjectVersion.txt inside the project
  • Optional UNITY_INSTALL_PATH is used only for local database building (ingest) to locate the Unity install
  • 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
  • First run or database updates require internet access; without it you must build the database locally
  • The downloaded database is ~20-30 MB and occupies local disk space
  • An incorrect UNITY_VERSION can cause API docs for the wrong version to be served
  • Databases are rebuilt weekly by CI, so version coverage may lag the newest Unity release
  • Third-party packages are not indexed and return no results
  • 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 Code, Cursor, WindsurfClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools50