unity-profiler-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNITY_PROFILER_PORT | No | Port used by the MCP server. Keep equal to the Unity EditorPrefs value Shin0112.UnityProfilerMcp.Port. | 17891 |
| UNITY_PROFILER_CAPTURES | No | Capture folder used by the MCP server. Defaults to the open Unity project's ProfilerCaptures folder. | <project>/ProfilerCaptures |
| UNITY_PROFILER_EXPORT_TIMEOUT_MS | No | Export timeout in milliseconds for the MCP server. The Unity bridge waits up to 15 minutes. | 900000 |
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 |
|---|---|
| profiler_list_capturesA | List saved Unity Profiler captures (.data) with size, time, and whether highlights/marker exports exist. |
| profiler_summaryA | Frame-time summary of one capture: estimated CPU/GPU frame time from .highlights (no editor needed) and main-thread frame time from the marker export if present. |
| profiler_exportA | Have the open Unity Editor load a capture and export per-marker main-thread statistics to .data.markers.json. Large captures can take minutes and block the editor. |
| profiler_top_markersA | Most expensive main-thread markers of one capture (exports first if needed). sortBy spikeAvg shows what grows in the slowest 5% of frames. |
| profiler_compareA | Compare two groups of captures (e.g. 3 runs of branch A vs 3 of branch B) per marker. Reports group means, the run-to-run spread inside each group, and flags differences larger than that spread. |
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 targets a distinct profiler workflow step: listing captures, summarizing one capture, exporting marker data, extracting top markers, and comparing capture groups. The export tool is a prerequisite for some analysis but its purpose is still clear and non-overlapping.
All tools share a consistent `profiler_` prefix, but the second segment mixes verbs (`list`, `export`, `compare`) with nouns/noun phrases (`summary`, `top_markers`). The pattern is still highly readable and predictable enough for an agent to infer usage.
Five tools is well-scoped for a Unity Profiler capture analysis server. Each tool covers a meaningful step in the workflow without redundancy or missing obvious operations.
The surface covers listing, summarizing, exporting, per-marker analysis, and group comparison for saved captures. Minor gaps exist, such as deeper per-frame or full marker hierarchy inspection, but core profiler workflows are supported.