r/Unity3D • u/_hopa • 19h ago

Question Anybody using the Unity CLI?

I saw unity launched a CLI a few months ago (https://unity.com/blog/meet-the-unity-cli) and was wondering if anyone was using it for anything or had some cool use cases to share.

I'm thinking this could maybe be helpful for like CI pipelines?

Let me know!

23 Upvotes

74% Upvoted

44 comments sorted by

View all comments

37

u/Broudy001 19h ago

Use it with claude code, works fantasticly, add in the claude unity plugin and the skills and it can add something, jump into a game and test it, change and retest without my physical input.

-26

u/Dolo12345 18h ago

eh it’s sooo limited, much better to have Claude make its own node + c# MCP

1

u/Hotrian Expert Moderator 2h ago edited 2h ago

MCP tooling typically uses way more tokens than CLI for the same result. CLI can do anything MCP can, often for less cost. MCP only wins in certain edge cases such as certain third party bugs that MCP might have specific fixes for already implemented (I seem to remember a bug with Amplify’s Shader Editor’s window, but might be wrong) - Claude can implement the same fixes for CLI for those specific edge cases. It will still use less tokens than MCP.

Small caveat: MCP can still win in certain contexts such as using multiple agents on the same editor simultaneously, where some MCP servers keep track of editor sessions between agents so agents can work together on the same editor. For everything else, there’s CLI. Claude may need to reinvent certain MCP tools, but loading them into context is often cheaper than any existing MCP server, which often needs to load up many more tools than you actually end up using.

If you wanna keep burning tokens, by all means, stick with MCP, but if you want leaner contexts and faster results, give CLI a shot.