Glitchrupt MCP Server
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| glitchrupt_statusA | Check permission, reduced motion, pause, busy state, cooldown, and installed app version. Opens app in background if needed. |
| glitchrupt_variantsA | List five original digital-crackle sounds. Listing does not play a cue. |
| glitchrupt_signalA | Request one brief visual glitch with optional sound. preview=true uses a test window. Duration is 300–1000 ms, volume 0–0.5. Native pause, reduced-motion and cooldown safeguards apply. completed means playback finished; timeout means outcome unknown. |
| glitchrupt_wait_for_approvalA | Register an actual wait on the user's approval. Plays two complete 600 ms glitches separated by 200 ms; repeats every 15 minutes until resolved. Reusing the same key is idempotent and does not replay or reset its timer. Returns registration, not completed playback. |
| glitchrupt_resolve_approvalA | Stop pending approval reminders. Supply exactly one key, or an owned key_prefix for session cleanup. Resolve as soon as the wait is answered, cancelled, or no longer blocks work; never clear another chat's keys. |
| glitchrupt_pending_approvalsA | List currently registered approval keys and milliseconds to their next reminders. Does not play a cue. |
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 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.