blipr-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLIPR_URL | No | Base URL of your Blipr server (hosted or self-hosted). | https://blipr.dev |
| BLIPR_TOPIC | No | Default topic used when a tool call omits one. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_alertA | Send a push notification to the user's phone via Blipr. Use this to reach the human: a long task finished, a build broke, you need approval, or you're blocked and need input. Priority 1 (silent) to 5 (critical); defaults to 3. |
| send_criticalA | Send a priority-5 critical page. Use ONLY for things that genuinely cannot wait (production down, urgent approval, safety). Bypasses silent/Focus when the Blipr app has Apple's Critical Alerts entitlement enabled; otherwise it is delivered as time-sensitive. |
| askA | Send a yes/no question (or, with |
| request_ackA | Send a message that needs the human to acknowledge it, and BLOCK until they tap 'Acknowledge', then return. Use this when the human must see and confirm receipt of something before you continue (a heads-up they have to read, a checkpoint reached, 'I'm about to start the long run'). The call does not return until the human acks or it times out. Returns { responded, message_id, topic } plus |
| check_replyA | Look up whether the human has replied to a question or ack you sent earlier — use it to resume after |
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 5 tools
Each tool maps to a distinct interaction mode: blocking question (ask), blocking acknowledgement (request_ack), non-blocking notification (send_alert), escalation (send_critical), and async polling (check_reply). The one soft overlap is send_alert vs send_critical, since send_alert at priority 5 does nearly the same job as send_critical; ask vs request_ack is clarified by their descriptions but still requires reading to distinguish.
All names are lowercase snake_case and four of five follow a verb_noun shape (check_reply, request_ack, send_alert, send_critical). The bare verb `ask` is the only deviation, and it is short and unambiguous rather than genuinely inconsistent.
Five tools is tightly scoped for a human-in-the-loop notification/approval service, and each one covers a genuinely different interaction pattern (ask, ack, notify, escalate, resume). Nothing looks like a redundant wrapper or a filler tool.
The core lifecycle — send notification, page critically, ask a question, request an ack, and resume a timed-out call — is fully covered. Minor gaps remain: no non-blocking question send (all questions block), no message listing/cancel/history, and send_alert's description doesn't state that it returns a message_id, which would make follow-up polling awkward.