#Open Source Unity MCP Lens

1 messages · Page 1 of 1 (latest)

honest anchor
#

I finally made unity-mcp-lens public.

It’s a standalone Unity MCP package for connecting the Unity Editor to external agents like Codex and other standard MCP clients.

Main goals:

  • lower-noise tool sync
  • narrower model-facing tool exposure
  • compact outputs
  • telemetry for measuring payload, context, and control-plane noise

I’ll be maintaining and hardening it through real dogfood testing in Unity game development, and adding new tools as real use exposes gaps or missing functionality.

Repo:
https://github.com/becool3000/unity-mcp-lens

GitHub

Standalone Unity MCP package focused on token efficiency, lower-noise tool sync, narrow model-facing tool exposure, and telemetry for measuring payload, context, and control-plane noise. - becool30...

cunning sail
#

Hello @honest anchor
This sounds like a really interesting Unity MCP package! The focus on token efficiency and lower-noise sync is crucial for improving performance in complex applications. I’m particularly curious about the telemetry aspect—how are you measuring payload and context noise? Are there specific metrics or tools you’ve found most useful for tracking that?
Looking forward to learning more!

honest anchor
#

Cool I will be working on it more after tomorrow I will give you more details. Right now I have a usage tracker that tracks all mcp tool use and requests and other activity. It’s exposed as an editor tool in unity and I can save the reports and use them to inform the agent when I am working on ways to reduce usage. I am going through loops working on some of my game projects and different things in unity using the mcp then after doing some work i check the tool usage and basically interview the agent for ways to improve and any new tools that could improve the workflow. Basically I am just doing that loop over and over.

#

Im using mostly codex 5.4 model