Unity (test pending)
Bridge an AI to the Unity Editor — manage assets, control scenes, edit scripts, run tests. Uses CoplayDev’s MCP for Unity (MIT — successor to justinpbarnett/unity-mcp).
Bridge an AI to the Unity Editor — manage assets, control scenes, edit scripts, run tests. Uses CoplayDev’s MCP for Unity (MIT — successor to justinpbarnett/unity-mcp).
Slug: unity
Transport: stdio (local subprocess)
Auth: n/a (local subprocess — uses env vars, not an HTTP key)
Command: uv run --directory <unity-mcp-server-dir> server.py
Setup: In Unity: Window → Package Manager → Add package from git URL → https://github.com/CoplayDev/unity-mcp.git?path=/MCPForUnity#main. That installs the Python bridge under the package; replace <unity-mcp-server-dir> in the args with its absolute path (…/MCPForUnity/UnityMcpServer~/src). Requires uv. Confirm the server entry in github.com/CoplayDev/unity-mcp.
Blender
Drive Blender from natural language — build/modify 3D scenes, objects, and materials, then render. Runs the popular blender-mcp server (ahujasid) locally via uvx.
Unreal Engine (test pending)
Control Unreal Engine 5 from natural language — actors, Blueprints, procedural scene building. Uses the community unreal-mcp (chongdashu); Epic has no official MCP yet.