apkd/Conduit

- Robust: survives crashes, restarts, assembly reloads, and handles multiple agents and Unity instances.
- Context-efficient: conserves the agent's context window and saves tokens. Small number of versatile tools.
- Simple setup: one Unity package, one server exe, automated setup wizard. No dependencies, no pollution.
- Supports Linux and Windows, both in the editor and in development builds.
> [!WARNING]
> **Granting an AI agent access to Unity indirectly gives them escalated access to your machine.**
> Agents may be able to perform actions outside the regular sandbox through Unity.
> Have a backup strategy, and make sure your work machine is resilient to data loss.
Installation
1. Install the Unity package
- Window ⟶ Package Manager ⟶ + ⟶ *Install package from git URL*
- Paste this URL (the release branch points at the latest commit that passed all tests)
- Or you can also declare it directly in Packages/manifest.json instead:
2a. Just use the setup wizard
> [!TIP]
> The Unity package includes a wizard for setting up the MCP server.
> This lets you download the server executable and configure your installed code editors in just a few clicks.
You can find the setup wizard in Unity here:
***Edit → Preferences... → Conduit***
2b. Install the MCP server
> [!TIP]
> If you used the setup wizard, you can skip this step.
First, you need to grab the MCP server executable, and put it in your project (for a project-local installation) or some stable location on your computer (for a user-level setup).
Windows
Download conduit-win-x64.exe and move it to the location where you want to keep it.
For example, this PowerShell command installs it as conduit.exe in your user profile:
Linux
Download conduit-linux-x64, place it in the location where you want to keep it, and make it executable.
For example, these commands install it as conduit in ~/.local/bin:
NixOS
Conduit supports Linux x64 and includes .NET. With nix-command and flakes
enabled, you can try it or install it:
For your NixOS or Home Manager configuration, add Conduit to your flake:
Put inputs.conduit.packages.x86_64-linux.default in environment.systemPackages
or home.packages, then rebuild. Configure your MCP client to run conduit.
If you'd like an HTTP server, add these entries to your Home Manager module list:
Apply your Home Manager configuration, then point your MCP client at
http://127.0.0.1:5080. The service starts and stops automatically with your desktop
session. You can change the port with services.conduit.port.
Install Unity Hub (unityhub) separately if you'd like Conduit to launch Unity.
You can connect to an editor you've already opened without Hub.
To update a flake installation, run nix flake update conduit and rebuild your
configuration. For profile installations, run nix profile upgrade ;
nix profile list shows the entry name.
Manual build instructions
Install the .NET 10 SDK for your operating system.
Then clone this repository and publish the server:
The executable is written to Conduit.Server/publish/win-x64/conduit.exe on Windows or Conduit.Server/publish/linux-x64/conduit on Linux.
3. Configure your code editor
> [!TIP]
> If you used the setup wizard, you can skip this step.
Replace the executable paths in the examples below with the path where you installed the MCP server.
Select your editor...
Codex
Configure the MCP server in either location:
- **Unity project:** .codex/config.toml. Codex loads this file after the project is trusted.
- **User account:** %USERPROFILE%\.codex\config.toml on Windows, or ~/.codex/config.toml on Linux.
stdio | Windows (Native)
stdio | Windows (WSL)
stdio | Linux
http
approve tool calls
To avoid going insane from having to approve every tool call separately:
Claude Code
Configure the MCP server in either location:
- **Unity project:** .mcp.json.
- **User account:** %USERPROFILE%\.claude.json on Windows, or ~/.claude.json on Linux.
The commands below create the **Unity project** configuration. Replace --scope project with --scope user to configure the **User account** instead.
stdio | Windows (Native)
stdio | Windows (WSL)
stdio | Linux
http