
Unity MCP Server
io.github.rachitkumarrastogiPublished by GitHub account rachitkumarrastogiv1.7.0Updated Oct 24, 2026
MCP server for Unity: 130+ tools, Unity 6 skills, AI/ML discovery. No Editor.
Overview
A local MCP server that gives AI assistants read-only access to a Unity project's files, settings, scenes, prefabs, scripts and assets without opening the Unity
- What you can do
- Inspect project and build configuration: project info, build scenes, player, quality, physics, graphics, audio, XR and version control settings, packages and Unity Hub projects. Explore code and assemblies: list scripts and assembly definitions, find scripts by content, read a script's public API, and trace assembly dependencies and cycles. Survey scenes and prefabs: list scenes, summarize hierarchies, find objects by component or tag, and inspect prefab contents and dependencies. Browse assets and references: search by name or extension, read .meta files, find what references an asset, and detect broken asset or script references. Review content areas such as materials and shaders, animator
- When to use it
- Useful when an assistant needs to answer questions about an existing Unity project or help with refactoring, audits and release checks without the Unity Editor running. Suited to developers, testers and designers who want project structure, asset references and build readiness surfaced in chat.
- Requirements
- Runs as a local process over stdio; needs Node.js 18+ and the UNITY_PROJECT_PATH environment variable set to the absolute path of the Unity project root. The server is built from source (npm install and build) and configured in the MCP client's config file.
Installation
In SourceWeft
- Open Unity MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Unity MCP Server
MCP server for Unity — Gives AI assistants structured access to your Unity project from any MCP-capable IDE or app. No Unity Editor required.
[Cursor / IDE → Unity MCP Server → Unity Project]
Your IDE talks to this server; the server reads your Unity project folder and answers with project info, build scenes, scripts, prefabs, and more — so the AI can help without opening the Editor.
Overview
- Editor-free — Reads only from the project filesystem.
- One server, many projects — Set
UNITY_PROJECT_PATHper project in your MCP config. - MCP-native — Works with any client that supports the Model Context Protocol (tools over stdio).
Supported IDEs and clients
This server uses the standard MCP protocol over stdio and exposes tools. Any IDE or app that can run an MCP server and pass environment variables will work. Commonly used clients include:
Configuration is the same everywhere: command = node, args = path to dist/index.js, env = UNITY_PROJECT_PATH = your Unity project root. See Configuration below for a Cursor example; other clients use the same structure in their own config format.
Tools
Expand a category below to see the tools it includes.
📦 Project & build
💻 Code & assemblies
🎬 Scenes & prefabs
📁 Assets & references
🎨 Materials & shaders
🎞️ Animation
🖼️ 2D & sprites
✨ Rendering
📝 TextMeshPro & UI
🎮 Input
🌐 Addressables & localization
🔊 Audio
🧪 Testing & docs
🔄 CI & version control
🔌 Integrations (config discovery only)
🧱 Unity 6 coverage
⚡ Speed & productivity
🤖 AI & ML
🔍 Meta
Using search_tools — Pass an optional query to filter tools by name, description, or category. Omit query to get the full catalog grouped by category.
All tools read from the project filesystem only.
Real-life examples
Copy-paste these into Claude, Cursor, or any MCP client (with this server configured and UNITY_PROJECT_PATH set). The AI will pick the right tools.
What to type in Claude / Cursor or any other MCP Client
In Claude, Cursor, or any MCP client, ask in natural language; the AI picks the right tool. Use the Example prompt to type column in each tools table above — those are the phrases to type in chat to get that result.
Prerequisites
- Node.js 18+
- UNITY_PROJECT_PATH — Absolute path to your Unity project root (set in your MCP client)
Installation
The server uses stdio; your MCP client starts it automatically.
Configuration
Example for Cursor (same idea for Claude Desktop, VS Code + MCP, Windsurf, etc.):
Replace the paths with your actual paths. For Claude Desktop, add an entry under mcpServers in claude_desktop_config.json with the same command, args, and env. For VS Code, use your MCP extension’s config to add the server and UNITY_PROJECT_PATH. Other clients follow the same pattern in their own config files.
Development
- Run built:
node dist/index.js - Run dev:
npm run devornpx tsx src/index.ts
Integration with Unity Editor
-
Current workflow: The AI runs inside your IDE (Cursor, VS Code with MCP, Claude Desktop, Windsurf, or another MCP-capable client). This server provides the AI with read-only access to your project (scenes, scripts, settings, and related assets). You run Unity Editor separately to open scenes, enter Play mode, and build. The AI uses the server to inspect the project and to suggest changes, answer questions, and assist with refactoring.
-
Future compatibility: This server implements the standard MCP protocol over stdio and requires a single environment variable (
UNITY_PROJECT_PATH). If Unity Editor gains built-in MCP client support, you could connect it to this server using the same configuration: commandnode, arguments pointing todist/index.js, andUNITY_PROJECT_PATHset in the environment. No changes to this codebase would be required.
Security
This repository does not include game code, assets, or secrets. The Unity project path is supplied at runtime by your MCP client. The server is suitable for public and private use.
Documentation
- MCP Registry — Discover and install this server from the official registry.
- Guides: Quick start · Publish · Tools by role
- Skills: Unity-domain agent skills
- Changelog: CHANGELOG.md
Source: README.md at commit 33fbb7e
Tools
0Version history
1- v1.7.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.