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, MCPShortlist candidateGitHub MCPMCP100 Recommended
Task fit
Best for
  • Using the publisher-documented Unity MCP integration to inspect and modify scenes, assets, scripts, and Editor state
  • Repository, issue, pull-request, and code context
  • Teams that can issue a narrowly scoped PAT or use the hosted OAuth flow
  • Read-only GitHub investigation using restricted toolsets
Not ideal for
  • Autonomous game-development decisions or projects that cannot run the documented Unity integration
  • Git hosting outside GitHub
  • Users unable to run Docker for the documented local configuration
  • Workflows that need only a small amount of public repository context
Avoid when
  • The connected model must not see project content or automated Unity changes cannot be tested and reverted
  • You cannot restrict the token to the necessary repositories and scopes
  • The agent must not receive private repository, issue, pull-request, or user data
  • Your organization has not approved the OAuth app or PAT policy
Provenance
Provenance details

Community implementation

io.github.IvanMurzak · Publisher source ↗

First-party MCP

GitHub · Publisher source ↗

Maintenance
Maintenance details

Repo: Aug 10, 2026

Package: Not documented

Repo: Sep 22, 2026

Package: Not documented

Popularity evidence
GitHub stars

4,221

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

33,158

GitHub stars · checked 2026-09-24T04:14:26.342000Z

Shared-package downloads / 30 days

7,813

shared-package downloads / 30 days (not MCP-specific) · checked 2026-09-08

Not documented
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✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
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.Hosted service supports OAuth; local stdio uses GITHUB_PERSONAL_ACCESS_TOKEN. GitHub recommends minimum scopes, separate tokens, rotation, and environment-variable handling.
CostThe Apache-2.0 project lists no MCP fee. Unity, model, hosting, and cloud-service costs are not documented.The open-source server is MIT licensed. GitHub account, Copilot, Enterprise, Actions, API, or other product charges and limits may apply independently.
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.Access follows the authenticated GitHub identity and granted OAuth/PAT permissions. The server supports tool allow-lists, read-only mode, repository-oriented toolsets, and lockdown mode; write tools remain possible unless read-only mode is enabled.
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.Repository contents, issues, pull requests, users, actions, and other enabled GitHub API data may be returned to the MCP client. The local server passes requests to GitHub; the hosted server is operated by GitHub. Do not place PATs in committed configuration.
Limitations
Tradeoffs
  • Direct Unity integration speeds iteration, but installation spans the Editor and MCP client and generated changes can leave project state invalid.
  • The default local toolsets include repositories, issues, pull requests, users, and context; limiting toolsets reduces capability and context size.
  • Local Docker keeps the MCP process local but still sends authorized requests to GitHub APIs.
  • PAT setup is explicit and portable, while hosted OAuth is easier but relies on GitHub's remote MCP service.
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.A broadly scoped token plus write-capable tools can alter repositories and collaboration records. Prefer fine-grained credentials, repository restriction, explicit toolsets, GITHUB_READ_ONLY=1, and lockdown mode where public-content prompt injection is a concern.
Evidence date
Editorial review2026-08-112026-07-24
Candidate evidence2026-08-14T18:46:26.000Z2026-09-24T04:25:05.554391Z

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

Read the evidence method →