Glitchrupt MCP Server
Related Servers
Alternatives to Glitchrupt MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI agents send desktop notifications during tasks, ask for attention, and report completion. Supports macOS, Linux, and Windows, with optional webhook delivery.833-
- AlicenseBqualityBmaintenanceMCP server that lets Claude Desktop or another MCP client trigger macOS sound and visual notifications through a task_status tool.116MIT
- AlicenseAqualityDmaintenanceA local MCP server that rings a bell through your speakers to provide audible notifications when AI completes tasks or needs attention.2MIT
- AlicenseBqualityDmaintenanceAn MCP server that lets LLM agents dispatch native OS notifications when a task finishes. It supports cross-platform desktop notifications, task tokens for updates, mobile bridges, and quiet hours.2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for macOS native notifications with 67 AI brand icons and system sound support, enabling AI agents to send desktop notifications via one-line tool calls.MIT
- AlicenseAqualityDmaintenanceA lightweight MCP server that enables sending native desktop notifications with action buttons and text replies, compatible with any MCP client.129 npm1MIT
TDQS
Scored across 6 tools
The tools cover mostly distinct actions: status check, variant listing, glitch signaling, and an approval lifecycle of wait/resolve/list. The closest overlap is between status and pending_approvals, but their descriptions clarify that one is a general readiness check and the other lists specific approval keys.
All tools use a consistent glitchrupt_ prefix and snake_case. Most are noun/resource names (status, variants, signal) while approval tools use verb phrases (wait_for_approval, resolve_approval), which is a minor but readable deviation.
Six tools are well-scoped for a focused glitch/sound and approval-control server. Each tool has a clear, non-redundant role in checking state, listing sounds, emitting cues, and managing approval waits.
The approval workflow has a coherent lifecycle: wait, resolve, and list pending approvals. Signal and variant discovery are covered, but there is no explicit tool for configuring settings such as reduced motion or cooldown beyond checking status.