ios-instruments-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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesB | List available iOS simulators and physical devices. |
| list_templatesA | List all Instruments profiling templates installed on this Mac. |
| analyze_launchB | Record an App Launch trace and report which methods hurt startup time with fix suggestions. |
| analyze_launch_traceB | Analyze an existing .xctrace file recorded with the App Launch template. |
| analyze_allocationsB | Record an Allocations trace and report peak memory, top allocation types, and fix suggestions. |
| analyze_allocations_traceB | Analyze an existing .xctrace file recorded with the Allocations template. |
| analyze_leaksB | Record a Leaks trace and report all memory leaks with retain cycle detection and fix suggestions. |
| analyze_leaks_traceB | Analyze an existing .xctrace file recorded with the Leaks template. |
| analyze_time_profilerC | Record a Time Profiler trace and report hot methods consuming the most CPU time. |
| analyze_time_profiler_traceC | Analyze an existing .xctrace file recorded with the Time Profiler template. |
| analyze_networkB | Record a Network trace and report slow requests, transfer sizes, and optimization suggestions. |
| analyze_network_traceC | Analyze an existing .xctrace file recorded with the Network template. |
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 12 tools
Each tool has a clearly distinct purpose. The pairing of 'record+analyze' vs 'analyze existing trace' for each profiling type is unambiguous, and the helper tools are unique.
All tools use consistent snake_case with a verb_noun pattern. The base verb 'analyze' for recording+analyzing and the suffix '_trace' for analyzing existing traces forms a clear and predictable convention.
With 12 tools covering major profiling templates (allocations, launch, leaks, network, time profiler) plus device and template listing, the count is well-scoped for the domain.
The set provides recording and post-analysis for all major instrument types, plus necessary discovery tools. No obvious gaps for typical profiling workflows.