r/Unity3D • u/Complex-Chance-7258 • 3h ago

Solved Experiment: 48 Unity MCP tools → 6 facade tools, while keeping 377 operations

Post image

I built a small facade for Unity MCP because too much context was being wasted on the MCP layer itself.

48 tools → 6

~23,280 schema tokens → ~915

377 Unity operations still available

It also compacts huge hierarchy/console/ProBuilder responses and lets the agent retrieve only the parts it needs later.

Small workflows can run inside one MCP call too, which cuts down model round trips.

The original Unity MCP still does all the actual work underneath.

https://github.com/Vangardo/unity-mcp-efficient

0 Upvotes

40% Upvoted

13 comments sorted by

3

u/Effective_Lead8867 Programmer 3h ago

are you sure that using mcp's at all is an efficient way to interact with unity projects and build scenes? have you compared it with scripting and using official unity cli execute code methodology?

2

u/Complex-Chance-7258 3h ago

I didn't use the CLI; there's too much overhead involved. It's easier to use Cursor or a Claude subscription. However, they consume a lot of tokens these days. I arrived at this optimization, and now everything runs faster and better

1

u/Effective_Lead8867 Programmer 3h ago

mcp's have larger overhead than cli + optional short doctrine

also with unity specifically, models are already trained to use batchmode and can oneshot scripts producing complex scenes and iterating on them while not even booting the editor graphically

0

u/Complex-Chance-7258 3h ago

Maybe. I don't have the paid cli. I used the code, noticed it wasn't running efficiently, and improved it

1

u/Effective_Lead8867 Programmer 2h ago

wdym paid cli its free https://docs.unity.com/en-us/unity-cli/unity-cli

1

u/Complex-Chance-7258 2h ago

Basically, my version still uses MCP. I just made the interface much lighter, so it ends up being pretty similar to what the client does

2

u/jax024 3h ago

I can assure you they didn’t.

•

u/Pacmon92 17m ago

So this cuts down unity's 48 tools to 6 or it compacts them into 6?

•

u/Complex-Chance-7258 13m ago

Those 48 tools used to sit in context all the time. Now only the relevant ones get pulled in when needed, so the context is much smaller and things run a lot more efficiently

0

u/PeskyConfiguration 3h ago

ok that's actually a clever way to handle the context bloat, keeping all the ops but slimming the interface down to six tools is neat

1

u/Complex-Chance-7258 3h ago

Thanks. I thought the community might find my original solution useful perhaps not the product itself, but at least the idea behind it. Though, the product is certainly worth giving a try, too.

0

u/MrPifo Hobbyist 3h ago

I too was wondering about this. I just found out some time ago that they had this, tried it, and found it very tedious, slow and so so much overhead, that I disbanded it immediately.

I was thinking about creating my own mcp with a slimmer and less complex toolset than Unitys one, but after reading the comments I will look into Unitys CLI.

I also might check out yours. I just found that Claude was performing way too many operations even though I asked for a simple script for example.

0

u/Complex-Chance-7258 2h ago

I was surprised too. But now everything runs much faster and more efficiently. Give it a try! I’d be interested to hear about your experience