mcp-server-macos
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.
Tools that act on the Mac this server runs on, which is the user's own computer. Reading tools are safe to call at any time. Tools that show, change or send something are seen by the user: call them when the user asked for it, or when it clearly serves what they asked.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_notificationA | Show a notification on this Mac, in the top-right corner of the screen and in Notification Center. macOS shows it as coming from Script Editor. Text over 4096 characters is clipped. Don't put a secret in a notification: other processes of the user can see its text while it's being posted. |
| get_system_infoA | Get information about this Mac: the macOS version and build, the model, the processor, the installed memory, the computer's name and how long it has been running. |
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 2 tools
The two tools have completely distinct purposes: one posts a user-visible notification, the other retrieves system information. There is no plausible way to confuse them or misselect between them.
Both names follow the same clear snake_case verb_noun convention: send_notification and get_system_info. The pattern is predictable and readable.
Two tools is quite thin for a server named mcp-server-macos, which suggests broad macOS integration. Each tool is well-scoped, but the surface feels minimal rather than complete.
The server exposes only notification sending and system information, leaving obvious macOS-related operations unaddressed. Agents needing app control, file interaction, or other system actions would hit dead ends.