What is Boop?
Boop is a notification inbox for developers who want application events delivered to their phones while keeping the event store on their own server. Applications submit events using project API keys. The Go server redacts configured sensitive keys before storage in SQLite and sends notifications directly through Apple APNs, without a hosted relay or telemetry. Push payloads contain the title, body and event identifier; the iOS app retrieves full details from the server.
The server runs through Docker Compose or a standalone binary for Linux, macOS or Windows, with its Svelte web interface embedded. The interface manages projects, devices, retention and notification settings. The SwiftUI iOS app must be built and signed by the operator, then paired using a QR code. Without APNs credentials, events remain available in the inbox but do not generate push notifications.
Events can include exceptions, stack traces, context, breadcrumbs and action buttons. Repeated fingerprints can be grouped for display, while silence rules suppress matching pushes without discarding events. Boop also accepts server-side Sentry SDK error reports and exposes structured event context through a read-only MCP endpoint. It contains no built-in language model.
Key capabilities
- Event ingestion Accepts structured application events through a project-key API, language clients or server-side Sentry SDKs.
- Notification delivery Sends pushes directly through Apple APNs and lets paired iOS devices retrieve full event details.
- Inbox controls Filters events, groups repeated fingerprints and silences matching notifications while retaining their records.
- Sensitive-data handling Redacts configured keys within event data before storage and provides configurable retention.
- Event actions Displays action buttons in notifications and event details, with Markdown export and sharing on iOS.
- Agent access Provides read-only MCP tools to list projects, search events and retrieve full payloads or grouped occurrences.
Where Boop fits
Boop fits alongside deployment pipelines, scheduled jobs, backup scripts and application error reporting. These systems submit events to a shared inbox, where developers can review context and receive selected notifications on an iPhone. Documented connection paths include GitHub Actions, Elixir, Node.js, ErrorTracker and a community-maintained Laravel client.
Before deployment, operators need to check server reachability from the phone, writable database storage, backups, authentication and Apple push credentials. The iOS app requires building and signing. Leaving administrator credentials unset leaves the interface and administrative endpoints open, so that configuration requires protection behind an operator-controlled proxy or private network. Sentry ingestion credentials must remain server-side because their DSN key can write events. Grouping alone does not reduce pushes; silence rules are needed for that.
Install
git clone https://github.com/chrisgreg/boop && cd boopReviews of Boop
Be the first to share your experience with Boop.
Write a review
Loading review form…
Alternatives to Boop
AppriseApprise is an open-source Python library and CLI that sends notifications to many services, including chat, email, SMS and desktop, through one interface.
LiveKitLiveKit server is an Apache 2.0 WebRTC selective forwarding unit written in Go. It routes audio, video and data between browsers, apps, phones and AI agents, runs as a binary, Docker image or Helm chart, and scales across nodes with Redis.
MergeMerge offers one Unified API per category (HRIS, ATS, CRM, accounting, ticketing, file storage, knowledge base, chat), Agent Handler for MCP tool access by AI agents, Gateway for LLM routing and Merge for Workforce.