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.
| Evidence field | Klavis AI MCP infrastructureShortlist candidate | MCP Unity Editor (Game Engine)MCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP reviewed-detail:klavis-ai-mcp · Publisher source ↗ | Community implementation github:codergamester · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Sep 3, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | Not documented | 1,910 GitHub stars · checked 2026-09-24T04:14:16.259000Z |
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Klavis can broker OAuth for supported integrations; some self-hosted servers also accept direct provider tokens through configuration. | The WebSocket server defaults to localhost:8090. Remote instructions can bind it to 0.0.0.0; no bearer-token or OAuth mechanism is documented. |
| Cost | Provider and Klavis plan/usage costs may apply. | The publisher describes the MIT-licensed project as free and open source. Unity, Node.js, hosting, client, and model costs are separate. |
| Permissions | Permissions depend on each connected provider and integration. Individual tools may carry readOnly annotations, but the platform can also expose write-capable provider actions. | Executes Unity menus and controls scenes, GameObjects, components, materials, assets, packages, tests, logs, play mode, and project-state resources through a WebSocket bridge. |
| Data handling | Requests and provider credentials are mediated by the Klavis platform or self-hosted integration server depending on deployment. | Unity scenes, assets, project state, and console logs are read or modified locally and returned through MCP. Remote transmission, retention, and telemetry are not documented. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | High. This is integration infrastructure with many possible third-party accounts; tenant isolation, credential storage, audit, and revocation are core trust boundaries. | Can make destructive project changes, install packages, execute menu items, and control play mode. Keep the bridge loopback-only and supervise all writes and deletions in a version-controlled project. |
| Evidence date | ||
| Editorial review | 2026-09-11 | 2026-08-11 |
| Candidate evidence | 2026-09-11T00:00:00.000Z | 2026-09-24T04:25:05.554391Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →