Unity 6 And Cursor A Fully Structured Setup Guide
There are two completely different ways to pair Cursor with Unity 6, using it as your script editor, or connecting it directly to the running Editor through Unity's own MCP server. I set up both and documented every step.
Unity MCP Official Guide
Unity's own walkthrough for connecting Cursor, Claude Code, and other agents
unity.com
Unity MCP by CoplayDev
The open source MCP server I used, 47 tools, MIT licensed, supports Unity 2021.3 LTS through 6.x
github.com
Cursor Documentation
Official Cursor docs for configuring MCP servers inside the editor
cursor.com
Priya Nair
July 18, 2026
Two Different Questions Hiding In One Search
Unity 6 and Cursor actually covers two separate setups depending on what you actually want. The simple version is using Cursor as your script editor instead of Visual Studio, which has nothing to do with AI at all. The bigger version is connecting Cursor directly to a running Unity Editor through Unity's own MCP server, so Cursor can inspect scenes, read console errors, and edit GameObjects, not just text files. I set up both, in order, so you can stop at whichever level you actually need.
Setup One, Cursor As Your Script Editor
This is the version most people actually mean when they first ask this question. Unity does not care which code editor opens your C# files, it just needs to know where to send them.
- Open your Unity 6 project and go to Edit > Preferences on Windows or Unity > Settings on macOS
- Select External Tools from the left sidebar
- Under External Script Editor, choose Browse and point it to your Cursor executable
- Leave Editor Attaching enabled if you want breakpoint debugging to keep working
- Double click any C# script inside Unity, it should now open directly in Cursor
This alone is genuinely useful. Even with zero AI configuration, you now get Cursor's autocomplete, refactoring, and chat while editing Unity scripts, since Cursor still reads your whole project folder as a normal codebase. A lot of people stop here and that is a perfectly complete setup.
Setup Two, The Real Unity MCP Integration
This is where it gets genuinely different from any other code editor pairing. Unity ships an official MCP, short for Model Context Protocol, server that runs inside the Editor itself. Once connected, Cursor is not just editing text files anymore, it can inspect the live scene hierarchy, read console output in real time, and trigger actual Editor actions, all from a plain language prompt.
MCP support requires Unity 6 or newer. This will not work on Unity 2022 or earlier LTS versions, if you are on an older LTS, Setup One above is the only option available to you until you upgrade.
Connecting The Official Unity MCP Server
- In the Unity Editor, open Edit > Project Settings > AI > Unity MCP
- Confirm the Unity Bridge status shows Running, it starts automatically when the Editor loads
- Expand the Integrations section on that same settings page
- Select Cursor from the supported client list and click Configure
- This automatically writes the correct entry into Cursor's own MCP configuration file for you
// what the auto-generated mcp.json entry looks like in Cursor settings
{
"mcpServers": {
"unity-mcp": {
"command": "~/.unity/relay/relay_mac_arm64.app/Contents/MacOS/relay",
"args": ["--mcp"]
}
}
}The first time Cursor actually connects, Unity shows a Pending Connection message rather than accepting silently. Go back to Edit > Project Settings > AI > Unity MCP, review the client details, and click Accept. After that first approval, reconnects happen automatically without asking again.
What You Can Actually Prompt Once Connected
This is the part that changes the workflow, not just the tooling. Instead of writing a script and manually attaching it in the Inspector yourself, you can describe the outcome directly in Cursor's chat.
- Create a player controller and attach it to the Player object, no manual drag and drop into the Inspector needed
- Find the cause of the errors in the console and fix them, Cursor reads live console output, not just static log files
- List the components on the objects in the current scene, useful for onboarding into an unfamiliar project fast
- Execute the menu item GameObject/Create Empty, triggering real Editor actions through natural language
The key architectural difference. A normal code editor only ever sees your project's files on disk. Unity MCP exposes the running Editor's actual internal state, the scene graph, GameObjects, live console, so Cursor can answer questions and take actions that reading files alone could never support.
The Open Source Alternative I Also Tested
Alongside Unity's own first party MCP server, there is a well maintained open source option from CoplayDev with a wider tool catalog, 47 focused MCP tools at last count, MIT licensed, and it supports a broader Unity version range going back to 2021.3 LTS, not just Unity 6.
# install via Unity Package Manager, Add package from git URL
https://github.com/CoplayDev/unity-mcp.git?path=/MCPForUnity#main
# then inside Unity
# Window > MCP for Unity > Configure All Detected ClientsProblems I Ran Into
- Editor state matters, if a script has a compile error, MCP tool calls can fail until the error is resolved manually first
- The first connection approval step is easy to miss, if Cursor seems to hang on a Unity related prompt, check for a Pending Connection notice in Unity itself
- Multiple Unity Editor instances open at once need an explicit set_active_instance call in some MCP implementations, otherwise commands can route to the wrong project
- This is officially still beta territory, Unity's own documentation frames it as an exploration tool for now, not something to fully trust in a production pipeline yet
Treat MCP controlled Editor actions the same way you would treat any agent with write access to your project, review what it changed before committing, especially early on while you are still learning what kinds of prompts it handles reliably versus where it gets confused.
How I Actually Use This Day To Day
I use Setup One, Cursor as my script editor, for basically everything, it is simply a better editing experience than the default Unity workflow. I reach for the full MCP connection specifically when I am prototyping a new mechanic and want to describe the behavior in plain language rather than manually wiring up components, and when I am debugging a console error I do not immediately understand, since Cursor reading the live console output directly saves the copy paste step entirely.
The Result
Setup One took about two minutes and immediately improved day to day script editing. Setup Two took closer to fifteen minutes including the first connection approval, and changed how I prototype specifically, describing a behavior and watching it get wired into the scene directly felt like a genuinely different workflow, not just a faster version of the old one.
Verdict. If you just want a better code editor for Unity 6 scripts, Setup One alone is worth doing today, it takes two minutes. If you want Cursor to actually understand and manipulate your live scene, the official Unity MCP integration delivers on that, with the caveat that Unity itself still labels this beta, so keep reviewing what it changes.
Should You Bother
Every Unity 6 developer should at least try Setup One, there is no real downside and it costs nothing. Setup Two is worth the extra fifteen minutes if you regularly prototype new mechanics or spend real time debugging console errors, it genuinely removes a layer of manual busywork. If your project is close to shipping and stability matters more than speed right now, it is reasonable to wait for MCP support to leave beta before wiring it into your main workflow.
Unity MCP Versus Unity's Own AI Assistant
It is easy to conflate these two, since they share the word MCP and both live inside the same settings menu. Unity's built in AI Assistant is a first party chat and agent layer running inside the Editor. Unity MCP Server is a different feature that exposes the Editor itself as a set of tools an *external* client like Cursor can call. One is Unity's own assistant, the other is a bridge letting your outside tool of choice drive Unity directly. You can use either independently, or both together, they are not mutually exclusive.
Questions I Had Before Setting This Up
Does this work with Unity 2022 LTS? No, the official MCP integration specifically requires Unity 6 or newer. If you are on an older LTS and cannot upgrade yet, some of the third party community MCP servers claim broader version support, but the officially documented path is Unity 6 only.
Does connecting Cursor to Unity cost anything extra? No additional Unity fee, the MCP Server itself is part of the Unity AI feature set. You do still need whatever Cursor plan or API key setup covers your actual usage of Cursor itself.
Can Claude Code use this the same way? Yes, Unity's Integrations list includes Claude Code and Claude Desktop alongside Cursor and Windsurf, the setup steps are nearly identical, just select the client you are actually using in the Integrations dropdown.
Is my project data sent anywhere by connecting this? The relay runs locally on your machine, connecting the local Unity Editor to your local Cursor installation. Review Unity's own MCP documentation for the specifics of what gets transmitted if this matters for a project with strict data handling requirements.
Official Unity MCP Versus The Community Options
- Unity's official MCP Server - built in, auto-configures Cursor through the Integrations panel, tightest integration with Unity's own AI Assistant and Gateway
- CoplayDev unity-mcp - open source, MIT licensed, 47 tools, supports Unity 2021.3 LTS through 6.x, useful if you are not yet on Unity 6
- CoderGamester mcp-unity - focused specifically on Editor automation, supports a wide client list including Codex CLI and GitHub Copilot alongside Cursor
- Community forks - several smaller projects exist with narrower tool sets, generally fine for experimentation, worth checking recent commit activity before relying on one for daily work
For most people starting fresh on Unity 6, the official server is the right starting point simply because the auto-configure step removes any manual JSON editing. Reach for one of the community options specifically if you need broader Unity version support or a different tool coverage than the official server currently ships with.