notch-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notch_stylesA | List the available notch readout styles with metadata on what each is for, plus the current display capability. Call this once before your first notch_status if you are unsure which style fits, or to check whether this Mac currently has a notch at all. |
| notch_statusA | Show or update a status readout in the notch. Call when starting long-running work and again as it progresses. Does not steal focus and needs no window. Always finish with notch_done or notch_error so the readout resolves instead of just vanishing. |
| notch_doneA | Resolve the current task: flash green, then auto-hide. Use for "complete" updates at the end of long work. |
| notch_errorA | Resolve the current task as failed: flash red and linger longer than a success. |
| notch_clearA | Hide the readout immediately. |
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 styles, setting a status, marking success, marking failure, and clearing. There is no overlap or ambiguity between them.
All tools share the 'notch_' prefix and use simple, readable lowercase names. However, the pattern is not strictly verb_noun (e.g., 'styles' is a noun, 'done' is an adjective), so there is a minor deviation from a consistent verb-first convention.
Five tools is exactly right for this server's scope. Each tool fills a necessary role in the lifecycle of displaying and resolving notch readouts without redundancy.
The tool set covers the full lifecycle: checking capability, showing/updating a status, and resolving as success, failure, or immediate clear. There are no obvious missing operations for the stated purpose.