Compared · unity
7 Unity MCP servers. Which one to use.
Every Unity server we index, with whether its source is still reachable and whether we hold a screening verdict. None currently carry a source-liveness flag.
Scope: 7 servers indexed from the MCP registry as of 2026-07-25. Servers whose authors never published to the registry are not listed here, so treat this as the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Unity API Documentation | io.github.Codeturion | no flag | REVIEW | 90 | pypi unity-api-mcp |
| Unity MCP Server | io.github.rachitkumarrastogi | no flag | REVIEW | 90 | npm unity-mcp-server |
| Patina Unity MCP | io.github.taygunsavas | no flag | REVIEW | 90 | npm com.taygunsavas.patina-unity-mcp |
| Funplay Unity MCP | io.github.FunplayAI | no flag | REVIEW | 85 | not published |
| FunseaAI Unity MCP | io.github.FunseaAI | no flag | REVIEW | 79 | not published |
| Unity AI Bridge | io.github.butterlatte-zhang | no flag | not screened | 62 | not published |
| io.github.IvanMurzak/Unity-MCP | io.github.IvanMurzak | no flag | REVIEW | 59 | docker docker.io/ivanmurzakdev/unity-mcp-server:0.17.1 |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.