Glitchrupt MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Glitchrupt MCP Server register an approval wait and play the fracture cue"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Glitchrupt
Your agent needs you. Give the screen a little attitude.
Twelve windows deep? Agent waiting on a question? Glitchrupt gives your desktop a 600-millisecond jolt: fractured pixels, a crack of digital static, then back to your business. The whole animation runs faster; every beat stays in.
It works over your other apps, even with Codex in the background. Everything runs on your Mac. Desktop images stay in memory and disappear after the effect; nothing is saved or sent away.
See the jolt

Entirely synthetic demo. No real desktop, chats, files, or screen recordings. It uses the app’s renderer at real speed: 600 ms → 200 ms gap → 600 ms. Watch with original sound, or see a still. Reminders repeat every 15 minutes while registered and stop when the agent clears the wait after your reply or unblock.
Related MCP server: bell-mcp
Pick your noise
Five original crackles: Classic, Fracture, Brownout, Arc, Stutter. Open the desktop tester and hit Compare all five. Windowed previews work without screen capture.
You stay in charge: switch sound off, pause agent cues from the menu bar, or quit. Agent requests share a five-second cooldown. Reduce Motion suppresses desktop effects.
Kick it off
You need macOS 14+, Xcode Command Line Tools with Swift, Python 3.11+, and uv.
./scripts/build.sh
open build/Glitchrupt.app
uv sync --locked
uv run --locked glitchrupt preview --variant classicFor the whole desktop, enable Glitchrupt in macOS Privacy & Security → Screen & System Audio Recording, then relaunch if asked. The app briefly covers each display with a distorted snapshot and removes the overlays when it finishes.
uv run --locked glitchrupt signal --variant fractureGive your agent the signal
Glitchrupt ships a CLI and a local MCP server. Agents can check status, list sounds, play a cue, register an approval wait, inspect pending waits, and resolve them.
uv run --locked glitchrupt status
uv run --locked glitchrupt mcpConnect it to Codex, or use the other-agent setup and tool reference. MCP registration is a separate setup step. For an approval wait, Glitchrupt plays 600 ms → 200 ms gap → 600 ms, then repeats every 15 minutes until the agent resolves it. Duplicate registrations do not replay the cue.
The optional Codex hook handles the initial double cue. Automatic repeats require an explicit wait/resolve workflow because the available desktop hook events cannot reliably confirm when an approval was answered. Approval setup and limits.
Make it yours
MIT licensed. Editable artwork, sound generators, Swift app, and Python tools live together. The visuals and sounds are original; this independent project has no affiliation with Marvel or Sony.
uv run --locked python -m pytest -q
./scripts/package.shPackaging creates local source/app ZIPs and checksums. The current app is signed for local testing; public releases need signing and notarization. See architecture, brand sources, and verification for the nuts and bolts.
Poke the human. Carry on.
Available Tools
6 toolsglitchrupt_pending_approvalsARead-only
List currently registered approval keys and milliseconds to their next reminders. Does not play a cue.
Inputs: no named parameters. Returns: object
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.
Inputs: key, key_prefix. Returns: object
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.
Inputs: sound, volume, preview, variant, +1 more. Returns: object
glitchrupt_statusARead-only
Check permission, reduced motion, pause, busy state, cooldown, and installed app version. Opens app in background if needed.
Inputs: no named parameters. Returns: object
glitchrupt_variantsARead-only
List five original digital-crackle sounds. Listing does not play a cue.
Inputs: no named parameters. Returns: object
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.
Inputs: key (required), sound, volume, preview, +1 more. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Pingstack monitors cron jobs and scheduled tasks with heartbeat checks, and checks websites, TCP ports, DNS records, SSL certificates and domain expiry. This MCP server lets your agent create, update, pause and delete checks, build dashboards and publish them as status pages, manage notification groups, and read incidents with their causes, uptime, run history and latency. Pause, delete and unpublish stay off until you turn them on. Browser sign-in, no API key needed.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Related MCP Servers
- 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
- AlicenseAqualityDmaintenanceA lightweight MCP server that enables sending native desktop notifications with action buttons and text replies, compatible with any MCP client.128 npm1MIT
- 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