Skip to main content
Glama
Shonas301

headless-unity-mcp

by Shonas301
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
unity_compileA

Import and compile all assemblies. The verdict is a error CS grep of the unity log, never the exit code — unity exits 0 on compile errors.

unity_testA

Run EditMode and/or PlayMode tests. The results XML is the evidence: a missing XML is a FAIL, any result="Failed" is a FAIL. Returns parsed per-platform totals.

unity_sceneA

(Re)generate a target's scene by invoking its configured scene_method. Only for projects that author scenes from code. Call unity_targets to list target names.

unity_buildB

Build the standalone player for a target, via its configured build_method. Call unity_targets to list target names.

unity_shotA

Launch the built player and screenshot its window by CGWindowID. Needs an existing build, the macOS Screen Recording grant, and an unlocked screen. Returns the PNG's path — read it in a throwaway subagent, not your main context.

unity_targetsA

List the build targets this project defines in unity-mcp.toml. Never takes the lock.

unity_statusA

Who, if anyone, holds the machine lock right now. Never takes the lock.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0

Scored across 7 tools

Disambiguation5/5

Each tool maps to a distinct Unity operation: screenshot, lock status, build, list targets, compile, test, and scene generation. Build vs compile are clearly differentiated by their descriptions, and no two tools appear to serve the same purpose.

Naming Consistency4/5

All tools share a consistent 'unity_' prefix, but the action words mix verbs (build, compile, test) with nouns (shot, status, targets, scene). This is mostly predictable but deviates from a pure verb_noun pattern.

Tool Count5/5

With 7 tools, the server is well-scoped for a Unity CI/headless workflow. Each tool covers a specific need without redundancy, and the count is well within the ideal 3-15 range.

Completeness4/5

The tool surface covers the core lifecycle: build, compile, test, screenshot, and scene generation, plus target listing and lock status. Minor gaps like explicit lock release or raw log retrieval are workarounds, but the main workflows are complete.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources