butterlatte-zhang/unity-ai-bridge
by Various
Remote-control Unity Editor from any AI IDE — 62 tools including AI-powered profiling & light probes. File-based IPC, zero dependencies.
MCP
butterlatte-zhang/unity-ai-bridge
Added 1 June 2026
Overview
A C# plugin that exposes 62 Unity Editor tools via file-based IPC, enabling remote control from any AI IDE. It uses zero external dependencies and includes profiling and light probe automation.
Best for
Best for
Developers who want to control Unity Editor programmatically from AI IDEs or automation scripts.
Use cases
- Automate Unity Editor tasks from an AI coding assistant
- Trigger profiling and light probe generation remotely
- Integrate Unity workflows into custom AI agent pipelines
How to use
Tools exposed
scene-openscene-savescene-createscene-list-openedscene-get-datascene-set-activescene-unloadgameobject-findgameobject-creategameobject-destroygameobject-modifygameobject-duplicategameobject-set-parentgameobject-component-addgameobject-component-destroygameobject-component-getgameobject-component-list-allgameobject-component-modifyassets-findassets-find-built-in
Tested with
Claude Code, Cursor, GitHub Copilot, Windsurf, Claude Desktop
Notes
A C# plugin that exposes 62 Unity Editor tools via file-based IPC, enabling remote control from any AI IDE. It uses zero external dependencies and includes profiling and light probe automation.
14 stars on GitHub. Last updated 2026-03-25. Licensed Apache-2.0.
Use cases
- Automate Unity Editor tasks from an AI coding assistant
- Trigger profiling and light probe generation remotely
- Integrate Unity workflows into custom AI agent pipelines
Pros
- Zero external dependencies simplifies setup
- File-based IPC works across different environments
- Covers a broad set of 62 editor tools
Cons
- Small community with only 14 GitHub stars
- File-based IPC may introduce latency for frequent commands
- Limited documentation and support for edge cases
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Zero external dependencies simplifies setup
- File-based IPC works across different environments
- Covers a broad set of 62 editor tools
Cons
- Small community with only 14 GitHub stars
- File-based IPC may introduce latency for frequent commands
- Limited documentation and support for edge cases
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Claude Code
Anthropic
Anthropic's terminal-native coding agent. Reads your repo, edits files, runs tests, ships PRs.
Cline
Cline
Open-source autonomous coding agent that lives inside VS Code. BYO model key, watch it work.
RooCode
Various
Roo Code gives you a whole dev team of AI agents in your code editor.
Continue
Continue.dev
Open-source AI code assistant for VS Code and JetBrains. Customisable, BYO model, built for enterprise.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.