macOS Tools 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| diskutil_listB | List all disks and partitions using |
| battery_statusB | Show current battery information reported by |
| network_servicesA | List configured network services as reported by |
| network_service_detailsB | Retrieve interface details (IP, subnet, router) for a network service. |
| system_profileC | Return structured data from |
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 clearly distinct purpose targeting different macOS system components: battery, disks, network services (listing vs. details), and system profile. There is no overlap in functionality, making tool selection straightforward for an agent.
The naming follows a consistent snake_case pattern with descriptive names (e.g., battery_status, diskutil_list). However, there is a minor deviation with 'network_service_details' and 'network_services' using slightly different naming styles (details vs. services) compared to the others, though still readable.
With 5 tools, the count is well-scoped for a macOS system utilities server. Each tool serves a specific, non-trivial purpose (battery, disks, network, system info), and there are no redundant or missing tools that would make the set feel too thin or bloated.
The toolset covers key macOS system areas (battery, storage, network, hardware/software info), but there are notable gaps in common system operations like process management, file operations, or user management. While the provided tools are useful, the surface is incomplete for broader system administration tasks.