apple-log-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 |
|---|---|
| apple_list_devicesB | List physical and simulated Apple devices known to Xcode/CoreDevice. |
| apple_start_live_logsB | Start a live Apple app log capture session. Console captures print/stdout/stderr; unified captures OSLog where supported. |
| apple_read_live_logsC | Read recent or incremental lines from a live Apple log capture session. |
| apple_stop_live_logsC | Stop a live Apple log capture session. |
| apple_list_log_sessionsA | List active and stopped Apple log capture sessions held by this MCP process. |
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 distinct purpose: listing devices, and managing log sessions with separate start, stop, list, and read operations. No overlap or ambiguity.
All tools follow a consistent 'apple_verb_noun' snake_case pattern (e.g., apple_list_devices, apple_start_live_logs). Perfect uniformity.
Five tools is an appropriate size for a focused log management server, covering essential operations without being overbearing.
The server covers the core lifecycle of log sessions (list, start, read, stop) and device enumeration. Minor gaps like log filtering or configuration are missing, but the main workflow is supported.