unity-mcp vs dsh-anchored-standard
unity-mcp: MCP for Unity integrates AI assistants like Claude and VS Code Copilot with the Unity Editor using the Model Context Protocol. This allows developers to use Large Language Models to manage assets, control scenes, edit scripts, and automate various tasks within Unity, streamlining game development workflows.; dsh-anchored-standard: dsh-anchored-standard is a set of community DeepSeek Harness agent presets that start a session under the Minimal condition, then promote to a small resident tool catalog and unlock heavier Standard tools on demand. It was tuned for DeepSeek V4 Pro and was frozen on 2026-09-10 after that model's retirement; new issues and PRs are no longer accepted.
TL;DR
- You develop games in Unity and want AI assistants (Claude, Cursor) to manage assets, inspect hierarchy, edit C# scripts, and run Editor commands via MCP.
- You want to automate scene setup, prefab creation, and repetitive Unity Editor tasks using natural language.
- You use Unreal Engine or Godot; unity-mcp connects strictly to the Unity Editor.
- You only write gameplay C# logic outside of Unity and do not need Editor-level RPC integration.
Studying how API-visible tool surface affects agent trajectories
Side-by-Side Comparison
unity-mcpdsh-anchored-standardFeatures
unity-mcpdsh-anchored-standardUse Cases
unity-mcpdsh-anchored-standardBest For
unity-mcpdsh-anchored-standardFAQ
Deploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.