官方说明7 个来源MCP 服务8 天前
german-krasnikov/unity-biome-mcp
MCP server for Unity Editor — 160 tools for scene, assets, animation, VFX, playtest & more
在 GitHub 查看 ↗直链 · 无中转页
官方说明="100%" alt="Concept illustration of an AI client sending a live MCP signal through Unity Biome MCP to the Unity Editor"> Control the Unity Editor from MCP-compatible AI clients or from chat inside Unity.** Inspect scenes, edit GameObjects, run playtests, and capture results through structured tools.
配置模板（请按你的客户端调整）
claude mcp add unity-biome-mcp -- npx -y unity-biome-mcp
这是根据仓库名生成的可粘贴骨架，命令行参数与包名请以该项目 README 为准。
- ★ 数取值
- 30 ★ · german-krasnikov/unity-biome-mcp · 取自该仓库的 GitHub 页面 · （2026-10-16 20:00:20 核对）
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 7 个来源列出
- 评分构成
- 综合分 703 · 30 ★ · 7 个来源 · mcp
常见问题（答案都来自我们的记录）
怎么安装？
我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。
它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
german-krasnikov/unity-biome-mcp；我们收录于 2026-10-09；最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。第三方质量标记
Unity Biome MCP
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
**Control the Unity Editor from MCP-compatible AI clients or from chat inside Unity.**
Inspect scenes, edit GameObjects, run playtests, and capture results through structured tools.
Quick Start ·
Documentation ·
Comparison ·
Changelog
Quick Start
Requirements: Unity 6 (6000.0 or newer), Git 2.14+ on PATH, and
uv. The MCP server does not need a separate Python
installation when it runs through uvx; optional Codex skill synchronization
requires Python 3.14 or newer on PATH. See the full
Getting Started prerequisites.
1. Install uv
macOS and Linux:
Windows:
2. Add the Unity package
1. In Unity, open **Window > Package Manager**.
2. Select **+ > Add package from git URL**.
3. Enter:
3. Configure your client
Open **MCP > Setup Wizard**, choose a client, and follow the result shown by the Wizard.
Configuration depends on the client. The Wizard may write a project configuration, run the configuration helper, copy a client-specific snippet, or defer configuration until In-Unity Chat starts. Restart the selected client when prompted. The Wizard configures the integration; it does not perform an end-to-end connection test.
Manual client setup guides
Use the matching guide:
Claude Code |
Claude Desktop |
Codex |
Cursor |
Junie |
Kimi |
OpenCode |
Rider AI Assistant |
VS Code |
Windsurf
For external OpenCode setup, do not use the Wizard's standard clipboard JSON:
OpenCode has a different configuration shape. Follow the
OpenCode guide.
4. Verify the first connection
For an external MCP client, keep the Unity project open, restart the client if
the Wizard asked you to, and send:
> Read the active Unity scene hierarchy at depth 2 and summarize its root objects.
The client should call:
A successful response contains the active scene hierarchy. If the call fails, open **MCP > Status > Diagnose** in Unity. For Chat-only verification, use the
Chat quick check. For command-line diagnostics, run:
See Getting Started for recovery steps and platform details.
Local development installation
Requirements for a source checkout: Git and Python 3.14 or newer.
> **Upgrading from older Python:** Install Python 3.14 via brew install python@3.14 (macOS), your system package manager (Linux), or python.org (Windows). Then run python install.py update to recreate the virtual environment.
The configuration helper supports claude-code, claude-desktop, cursor,
windsurf, vscode, codex, kimi, junie, and opencode.
Documentation
| Goal | Guide |
|---|---|
| Install and connect | Getting Started |
| Choose and configure an MCP client | Client guides |
| Install project-local AI guidance | AI Skills and Agents |
| Find a tool for a task | Tool Guide |
| Use batch safely | Batch Operations |
| Build Play Mode workflows | PlayTest DSL |
| Configure In-Unity Chat | Chat Backends |
| Extend Unity Biome MCP | Plugin Quick Start |
| Diagnose failures | Diagnostics |
What You Can Do
- **Scene and object editing:** inspect and modify GameObjects, components,
assets, materials, shaders, and UI.
- **Playtesting and verification:** run PlayTest DSL workflows, compile checks,
console checks, runtime diagnostics, and visual comparisons.
- **Animation and VFX:** work with clips, Animator controllers, Timeline,
particles, materials, shaders, and Shader Graph.
- **Efficient tool use:** group compatible operations with batch, request
Inspect scenes, edit GameObjects, run playtests, and capture results through structured tools.
Quick Start ·
Documentation ·
Comparison ·
Changelog
Quick Start
Requirements: Unity 6 (6000.0 or newer), Git 2.14+ on PATH, and
uv. The MCP server does not need a separate Python
installation when it runs through uvx; optional Codex skill synchronization
requires Python 3.14 or newer on PATH. See the full
Getting Started prerequisites.
1. Install uv
macOS and Linux:
Windows:
2. Add the Unity package
1. In Unity, open **Window > Package Manager**.
2. Select **+ > Add package from git URL**.
3. Enter:
3. Configure your client
Open **MCP > Setup Wizard**, choose a client, and follow the result shown by the Wizard.
Configuration depends on the client. The Wizard may write a project configuration, run the configuration helper, copy a client-specific snippet, or defer configuration until In-Unity Chat starts. Restart the selected client when prompted. The Wizard configures the integration; it does not perform an end-to-end connection test.
Manual client setup guides
Use the matching guide:
Claude Code |
Claude Desktop |
Codex |
Cursor |
Junie |
Kimi |
OpenCode |
Rider AI Assistant |
VS Code |
Windsurf
For external OpenCode setup, do not use the Wizard's standard clipboard JSON:
OpenCode has a different configuration shape. Follow the
OpenCode guide.
4. Verify the first connection
For an external MCP client, keep the Unity project open, restart the client if
the Wizard asked you to, and send:
> Read the active Unity scene hierarchy at depth 2 and summarize its root objects.
The client should call:
A successful response contains the active scene hierarchy. If the call fails, open **MCP > Status > Diagnose** in Unity. For Chat-only verification, use the
Chat quick check. For command-line diagnostics, run:
See Getting Started for recovery steps and platform details.
Local development installation
Requirements for a source checkout: Git and Python 3.14 or newer.
> **Upgrading from older Python:** Install Python 3.14 via brew install python@3.14 (macOS), your system package manager (Linux), or python.org (Windows). Then run python install.py update to recreate the virtual environment.
The configuration helper supports claude-code, claude-desktop, cursor,
windsurf, vscode, codex, kimi, junie, and opencode.
Documentation
| Goal | Guide |
|---|---|
| Install and connect | Getting Started |
| Choose and configure an MCP client | Client guides |
| Install project-local AI guidance | AI Skills and Agents |
| Find a tool for a task | Tool Guide |
| Use batch safely | Batch Operations |
| Build Play Mode workflows | PlayTest DSL |
| Configure In-Unity Chat | Chat Backends |
| Extend Unity Biome MCP | Plugin Quick Start |
| Diagnose failures | Diagnostics |
What You Can Do
- **Scene and object editing:** inspect and modify GameObjects, components,
assets, materials, shaders, and UI.
- **Playtesting and verification:** run PlayTest DSL workflows, compile checks,
console checks, runtime diagnostics, and visual comparisons.
- **Animation and VFX:** work with clips, Animator controllers, Timeline,
particles, materials, shaders, and Shader Graph.
- **Efficient tool use:** group compatible operations with batch, request
- 来源
- awesome · https://github.com/german-krasnikov/unity-biome-mcp
- 按领域浏览
- MCP 服务
- Traction
- 30 ★
- 收录于
- 昨天
更多MCP 服务
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。