unity-api-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNITY_VERSION | No | Unity version to serve. Valid values: a Unity 6 stream like "6000.3", or a major version like "6", "2023", or "2022". Used for version detection (highest priority, over UNITY_PROJECT_PATH). | 6 |
| UNITY_INSTALL_PATH | No | Override Unity install path (used for the ingest command only, not required to run the server). | |
| UNITY_PROJECT_PATH | No | Path to your Unity project. The server auto-detects the Unity version by reading ProjectSettings/ProjectVersion.txt from this path (lower priority than UNITY_VERSION). |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_unity_apiA | Search Unity API documentation by keyword. Use this to find Unity classes, methods, properties, and fields. Returns ranked results with summaries. Args: query: Search terms (e.g. "Physics Raycast", "SceneManager load", "Transform position") n_results: Max results to return (default 5, max 20) member_type: Optional filter — "type", "method", "property", "field", or "event" |
| get_method_signatureA | Look up the exact signature of a Unity API member by fully-qualified name. Use this when you know the specific API (e.g. from autocomplete or docs reference) and need its exact parameters, return type, and deprecation status. Args: fqn: Fully-qualified name, e.g. "UnityEngine.Physics.Raycast" or "UnityEngine.SceneManagement.SceneManager.LoadScene" Method overloads include params: "UnityEngine.Physics.Raycast(UnityEngine.Ray)" |
| get_namespaceA | Find the correct namespace and using directive for a Unity class or member. Use this when you need to know which namespace to import for a Unity type. Args: name: Class or member name, e.g. "SceneManager", "NavMeshAgent", "Rigidbody" |
| get_class_referenceA | Get a complete reference card for a Unity class — all public methods, properties, fields, and events. Use this when you want to see everything available on a class at a glance. Args: class_name: Class name with or without namespace. Examples: "Rigidbody", "Tilemap", "InputAction", "SceneManager" |
| get_deprecation_warningsA | Check whether a Unity class, method, or property is deprecated, and find the replacement. Use this before using any API you suspect might be outdated. Catches common mistakes like using FindObjectOfType (deprecated) instead of FindAnyObjectByType. Args: name: Class or member name to check. Examples: "WWW", "FindObjectOfType", "GUIText", "UnityEngine.Component.BroadcastMessage" |
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 5 tools
Each tool has a discernible niche: search_unity_api is keyword-based fuzzy lookup, get_class_reference returns a full class card, get_method_signature resolves a precise FQN, get_namespace maps a type to its using directive, and get_deprecation_warnings checks obsolescence. The main overlap is that get_method_signature already surfaces deprecation status and search can return members, but input-shape differences keep boundaries mostly clear.
All tools follow a predictable verb_noun pattern: get_class_reference, get_deprecation_warnings, get_method_signature, get_namespace, with search_unity_api as the single search verb. The convention is uniform and readable throughout.
Five tools is well-scoped for a documentation/API-lookup server. Each tool covers a distinct lookup mode (class card, signature, namespace, deprecation, keyword search) and none feels like filler.
The surface covers the core reference needs: finding classes/members, exact signatures, namespaces, and deprecation. Minor gaps exist such as inheritance hierarchy or example/usage lookup, but agents can work around these with the existing tools.