mcp-my-mac
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 |
|---|---|
| mcp_call_conda_infoA | Get comprehensive information about the Conda installation on this system. |
| mcp_call_mac_system_profilerA | |
| mcp_call_gpu_availableA | |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: conda_info focuses on Conda environments, gpu_available checks GPU availability and performance, and mac_system_profiler retrieves system information. The descriptions clearly differentiate their domains, making misselection unlikely.
All tools follow a consistent 'mcp_call_' prefix with descriptive snake_case suffixes (conda_info, gpu_available, mac_system_profiler). This uniform pattern makes the tool set predictable and easy to understand.
With only 3 tools, the server feels thin for a 'my-mac' system management scope. While the tools cover Conda, GPU, and system profiling, there are likely other Mac/system-related operations missing, making the set feel incomplete rather than well-scoped.
For a Mac system management server, there are significant gaps: no tools for file operations, process management, network utilities, or basic system commands. The three tools provide deep but narrow coverage, leaving many common system tasks unaddressed and likely causing agent failures for broader requests.