← Index
Compared · unity

8 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: 8 servers, mostly mirrored from the MCP registry as of 2026-08-13. Most servers whose authors never published to the registry are absent, so treat this as close to the registry's view rather than a complete census.

ServerPublisherSourceScreenedQualityInstall
Unity API Documentationio.github.Codeturionno flagREVIEW90pypi unity-api-mcp
Unity MCP Serverio.github.rachitkumarrastogino flagREVIEW90npm unity-mcp-server
Patina Unity MCPio.github.taygunsavasno flagREVIEW90npm com.taygunsavas.patina-unity-mcp
Funplay Unity MCPio.github.FunplayAIno flagREVIEW85not published
Hera Agent Unityio.github.NotNull92no flagREVIEW80npm hera-agent-unity
FunseaAI Unity MCPio.github.FunseaAIno flagREVIEW78not published
Unity AI Bridgeio.github.butterlatte-zhangno flagnot screened61not published
io.github.IvanMurzak/Unity-MCPio.github.IvanMurzakno flagREVIEW57docker 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.