Patina Unity MCP
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 |
|---|---|
| patina_callA | Execute an internal Patina Unity command. Targets the agent working-directory workspace by default; pass workspace to target a different project, or sessionId (from patina_sessions) to target one editor directly. |
| patina_capabilitiesA | Browse Patina's Unity command catalog without loading every command schema. Filter by category/search/command; set include_schema=true only for commands you intend to call. |
| patina_healthA | Return Patina server version, compact MCP surface status, bridge port, command count, and a broker summary (agentClientCount, unitySessionCount counting both connected and reloading sessions, reloadingSessionCount, and per-session detail). Pass include_unity_state=true to prove the routed Unity session is actually responding, not just registered. |
| patina_sessionsA | List active Unity sessions registered with the shared Patina broker, including workspace paths, health, state (connected|reloading|stale), and reloadCount. Check state="reloading" before assuming a failed call means Unity disconnected -- it may just be recompiling. |
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 4 tools
Each tool addresses a clearly distinct concern: command discovery, health status, session listing, and command execution. There is no overlap in purpose, and the descriptions reinforce their unique roles.
All tools share a consistent 'patina_' prefix with simple, readable names. 'call' is slightly verb-like compared to the noun-style others, but the overall pattern remains obvious and predictable.
Four tools is well-scoped for a bridge server that provides capability discovery, health checks, session monitoring, and command execution. Each tool earns its place without unnecessary bloat.
The toolset covers the complete workflow for this domain: discover available commands, check server health, list Unity sessions, and execute commands. No significant gaps are apparent for the stated purpose.