Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldAI Game Developer — Unity SKILLS, MCPWatchlist candidateDocker MCP GatewayMCP100 Selected
Task fit
Best for
  • Using the publisher-documented Unity MCP integration to inspect and modify scenes, assets, scripts, and Editor state
  • Running multiple MCP servers behind one stdio connection
  • Isolating catalog MCP servers in containers with restricted privileges and resources
  • Centralizing server profiles, secrets, OAuth, logs, and call traces
Not ideal for
  • Autonomous game-development decisions or projects that cannot run the documented Unity integration
  • Users who need only one simple remote MCP endpoint
  • Hosts where Docker Desktop or Docker Engine cannot run
Avoid when
  • The connected model must not see project content or automated Unity changes cannot be tested and reverted
  • You cannot review every downstream MCP server and profile permission
  • The agent must not be able to discover or add tools dynamically
  • Container isolation is being treated as protection from an over-privileged downstream credential
Provenance
Provenance details

Community implementation

io.github.IvanMurzak · Publisher source ↗

First-party MCP

Docker · Publisher source ↗

Maintenance
Maintenance details

Repo: Aug 10, 2026

Package: Not documented

Repo: Aug 13, 2026

Package: Not documented

Popularity evidence
GitHub starsNot documented

1,529

GitHub stars · checked 2026-08-14T18:46:26.000Z

Shared repository stars

3,893

Shared repository stars (not MCP-specific) · checked 2026-08-14T18:46:26.000Z

Not documented
External adoption evidence
  • github: repository stars: 3,893Non-comparable contextual signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
  • github: repository stars: 1,529Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationAuthorization modes are none, OAuth, or token, with none documented as the default. Token mode uses MCP_PLUGIN_TOKEN; cloud CLI login uses OAuth device flow.The gateway handles downstream server credentials and OAuth flows. The client connects locally over stdio by running `docker mcp gateway run`, optionally with a named profile.
CostThe Apache-2.0 project lists no MCP fee. Unity, model, hosting, and cloud-service costs are not documented.The open-source gateway documents no standalone usage fee. Docker Desktop licensing, Docker AI Governance invite-only features, container infrastructure, downstream MCP services, and AI-client charges may apply.
PermissionsProvides broad Unity Editor and runtime access, including project and asset writes, scene mutation, package changes, dynamic C# compilation and execution, reflection calls, profiling, and custom tools.The gateway exposes the servers and tools included in the selected profile. It starts catalog servers in containers with restricted privileges, network access, and resource usage, injects configured secrets, and can support OAuth. Dynamic MCP can additionally expose tools that discover, add, configure, remove, and execute servers during a session.
Data handlingAssets, scripts, scenes, runtime data, and results pass between the client, MCP server, and Unity plugin. Optional tool, prompt, and resource webhooks and cloud URLs are supported; retention is not documented.Tool requests and results pass through the local gateway to downstream MCP containers or remote services. Docker documents built-in logging and call tracing. Credentials are managed and injected by the gateway; downstream servers can still receive data and reach networks allowed by their configuration.
Limitations
Tradeoffs
  • Direct Unity integration speeds iteration, but installation spans the Editor and MCP client and generated changes can leave project state invalid.
  • Gateway isolation improves lifecycle and credential management but adds Docker runtime complexity and local resource use.
  • The MCP Toolkit is documented as Beta, and Dynamic MCP is experimental.
  • The gateway reduces direct host privileges, but network access and injected credentials still let downstream servers affect external systems.
Risk contextDefault unauthenticated mode plus broad writes, arbitrary C# execution, reflection, runtime access, and webhooks is high impact. Prefer local stdio, enable token or OAuth for HTTP, and restrict tools.Gateway safety is only as strong as the selected profile, catalog provenance, tool filters, network policy, and downstream credentials. Disable experimental Dynamic MCP unless required, use narrow profiles, verify signatures where available, inspect traces, and treat each downstream server as a separate trust decision. This review does not claim MCP100 execution testing.
Evidence date
Editorial review2026-08-112026-07-24
Candidate evidence2026-08-14T18:46:26.000Z2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →