Ring MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RING_DISABLED | No | Set to '1' to skip the popup entirely. The tool returns a stub response and logs to stderr. | |
| RING_TIMEOUT_MS | No | Default auto-dismiss timeout in ms (overrides the 5-minute default). |
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 |
|---|---|
| ringA | Ring a notification bell that opens a tab in a single always-on-top popup window. Multiple concurrent rings appear as tabs in the same window — the user switches between them and answers each independently. Each tab supports a free-form text reply, multi/single-select options (1-9 keys to toggle, Enter to submit, Esc to dismiss), or both. There is no auto-dismiss by default; the popup waits for the user. The user can also Mute the bell or Dismiss All from the toolbar. If the popup cannot be shown, the server falls back to an OS-native notification and reports the failure. |
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 confusion or overlap. The tool's purpose is singular and clearly described.
The single tool name 'ring' is a clear verb that matches its action. Since there is only one tool, consistency is trivially maintained.
The server has only one tool, which feels thin even for a narrowly scoped purpose. However, the tool is rich enough to cover the core functionality, making the count borderline but not unreasonable.
The tool fully covers the domain of ringing and managing notification bells, including multiple concurrent rings, replies, options, and fallback behavior. There are no obvious missing operations for the server's stated purpose.