Unity UIToolkit MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_uitoolkit_documentation | Provides Unity UIToolkit documentation reference with links and examples for specific topics like UXML, USS, UIElements, and other UIToolkit concepts. |
| get_uitoolkit_code_exampleA | Fetches actual code examples from Unity's official UI Toolkit manual code examples repository (https://github.com/Unity-Technologies/ui-toolkit-manual-code-examples). Use this to retrieve real implementation samples showing UIToolkit syntax and usage patterns. |
| fetch_unity_example_codeA | Fetches the actual source code content from a specific file in Unity's UI Toolkit examples repository. Use this when you have a code source reference (e.g., from tags in documentation) and need to see the actual implementation. |
| get_unity_script_referenceB | Retrieves Unity Script API reference documentation for UIToolkit classes and methods. Use this to get detailed API information. |
| convert_html_to_uxmlC | Provides guidance and examples for converting HTML markup to UXML format. Returns conversion patterns and best practices. |
| convert_css_to_uss | Provides guidance and examples for converting CSS styles to USS (Unity Style Sheets) format. Returns conversion patterns and best practices. |
| list_uitoolkit_components | Lists available Unity UIToolkit components and controls with brief descriptions. Useful for discovering what UI elements are available. |
| read_prerendered_docsA | Reads pre-rendered documentation for Unity UIToolkit. Returns documentation from either Unity's HTML manual (for UXML, USS, etc.) or from C# source code (for class API references). |
| list_prerendered_docs | Lists all available pre-rendered documentation files organized by type (manual and script-api). |
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
Tools have some overlap: get_uitoolkit_code_example and fetch_unity_example_code both deal with code examples from the same repository, while get_unity_script_reference and read_prerendered_docs both provide API reference information, creating potential ambiguity for an agent.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_uitoolkit_code_example, fetch_unity_example_code, convert_html_to_uxml), making the naming uniform and predictable.
With 5 tools, the server is well-scoped for its purpose of providing Unity UIToolkit documentation and code examples, avoiding unnecessary complexity while covering key functions.
The tool set covers code examples, API reference, HTML conversion, and documentation reading, but lacks search or listing capabilities, which could force agents to rely on exact references.