Unity Build Automation MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNITY_BUILD_ORG_ID | Yes | Organization ID | |
| UNITY_BUILD_API_KEY | Yes | Unity Build Automation API Key | |
| UNITY_BUILD_DEFAULT_PROJECT | No | Default project name or ID |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List all projects in the Unity Build Automation organization. |
| list_build_targetsA | List build targets for a project. Defaults to the configured default project. |
| list_buildsB | List builds for a project. Can filter by build target and status. |
| get_buildC | Get detailed information about a specific build. |
| get_build_logA | Get the build log for a specific build. Returns the last N lines to help investigate failures. |
| start_buildC | Start a new build for a build target. This is a write operation. |
| cancel_buildC | Cancel a running build. This is a write operation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: listing projects, build targets, or builds; getting build details or logs; and starting or canceling builds. The descriptions clearly differentiate similar-sounding operations like list_build_targets and list_builds.
All tool names follow a consistent snake_case verb_noun pattern (list_, get_, start_, cancel_), with only natural extensions like list_build_targets and get_build_log. No mixed conventions or vague verbs are present.
Seven tools are well-scoped for a build automation server, covering core listing, inspection, and control operations without redundancy. The count sits comfortably within the ideal 3–15 range.
The surface covers the essential build lifecycle: listing projects, targets, and builds; retrieving build details and logs; and starting or canceling builds. Minor gaps exist, such as no tool to inspect or manage build target configurations directly, but core workflows are fully supported.