mcp-macos-utils
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notifyA | Send a macOS notification with auto-detected project context |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'notify' has a clearly defined and distinct purpose.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'notify' is clear and follows a simple verb pattern.
A single tool is too few for a server named 'mcp-macos-utils', which implies a broader set of macOS utility functions. This feels thin and incomplete for the apparent scope.
Given the server name suggests macOS utilities, the single notification tool leaves significant gaps. There are no tools for other common macOS operations like file management, system info, or automation, making the surface severely incomplete.