Agenten stärken
Der eigene Befehl des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
npx -y @blipr/[email protected]Claude Code hat keinen Installationslink für einen lokalen Befehl. Kopieren Sie den Befehl unten und führen Sie ihn in einem Terminal aus.
claude mcp add blipr-mcp -- npx -y @blipr/mcp@0.6.3In einem Terminal ausführen.
{ "mcpServers": { "blipr-mcp": { "command": "npx", "args": [ "-y", "@blipr/[email protected]" ] } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
Starten@applogico/blipr-mcp@blipr/mcpnpx -y @blipr/mcpAn MCP server that lets AI agents send Blipr push alerts to your phone. Your agent finishes a long task, breaks a build, needs approval, or gets stuck — and it pages you. It can also ask you a question and block until you answer, for human-in-the-loop approval gates.
It's a thin stdio client: your MCP host (Claude Code, Cursor, …) launches it,
the agent calls a tool, and this process makes one outbound HTTPS POST to your
Blipr server. No inbound socket, nothing to host.
Claude Code ──stdio──► @blipr/mcp ──POST /blip/<topic>──► blipr.dev ──APNs──► 📱
No install needed — npx fetches it on demand. Point it at a Blipr server
(blipr.dev or your own self-hosted instance).
claude mcp add blipr \
--env BLIPR_URL=https://blipr.dev \
-- npx -y @blipr/mcp
{
"mcpServers": {
"blipr": {
"command": "npx",
"args": ["-y", "@blipr/mcp"],
"env": {
"BLIPR_URL": "https://blipr.dev"
}
}
}
}
Every blip goes to a topic, and each project should use its own, so alerts from different projects land separately on your phone. The topic for a call is resolved in this order:
topic tool argument — the agent passes it on the call. Always wins..blipr-topic file — per-project default. Put the topic name on the
first line of a .blipr-topic file in the project root; the server picks up
the nearest one from its launch directory upward (# lines are comments).BLIPR_TOPIC env var — global fallback, kept for backward
compatibility. Avoid it when one machine hosts several projects: a global
default makes every project ping the same topic.echo my-project-alerts > .blipr-topic
Then subscribe to the same topic (my-project-alerts) in the Blipr iOS app,
and you'll get the agent's pushes on your phone. On blipr.dev that subscribe,
made while signed in, is also what creates the topic, so do it before the
agent's first blip: publishing to a topic that does not exist returns 404. A
self-hosted server still creates the topic on the first publish.
send_alertSend a push notification. Parameters:
message (required) — the alert body.title — short bold title.topic — topic to publish to; pass it explicitly (falls back to
.blipr-topic, then BLIPR_TOPIC).priority — 1 silent · 2 low · 3 default · 4 high (plays a sound,
respects Focus) · 5 critical (breaks Focus).tags — emoji shortcodes, e.g. ["warning"].click — URL opened when the notification is tapped.markdown: render the body as Markdown (bold, italics, links, code). Off by default.send_criticalA priority-5 page for things that genuinely can't wait. Bypasses silent/Focus
when the Blipr app has Apple's Critical Alerts entitlement enabled; otherwise
it's delivered as time-sensitive. Also takes markdown.
ask — human-in-the-loop yes/no (blocks)Send a yes/no question to your phone and block until you tap an answer, then return it. This is an approval gate: the agent calls it before doing something consequential or irreversible and waits for your decision instead of guessing.
message (required) — the yes/no question.title — short bold title.topic — topic to publish to; pass it explicitly (falls back to
.blipr-topic, then BLIPR_TOPIC).priority — defaults to 4 (high) since it needs an answer.tags — emoji shortcodes, e.g. ["question"].markdown: render the body as Markdown (bold, italics, links, code). Off by default.timeout_seconds — how long to wait for your answer (default 120).Returns { responded, approved, value, message_id, topic }. Branch on
approved — it is true only when you tapped Yes, and false on No, a
timeout, or an error, so a refusal or non-answer can never be misread as a
go-ahead. On a timeout you get
{ responded: false, approved: false, reason: "timeout", message_id, topic }. If
it times out (or your MCP client cancels the call), you can still answer for
~30 min — pass the returned message_id to check_reply to resume.
Under the hood it publishes with reply: "binary", captures the message id
from the publish response, then long-polls
GET /blip/<topic>/<id>/reply?wait=… until you answer or the timeout
budget runs out.
request_ack — require acknowledgement (blocks)Send a message that you must acknowledge, and block until you tap
"Acknowledge". Use it when the human has to see and confirm something before
the agent continues. Same parameters as ask; publishes with reply: "ack".
Returns { responded, message_id, topic } plus replied_at when acked, or
{ responded: false, reason: "timeout", … }. As with ask, on a timeout you can
resume later with check_reply and the returned message_id.
check_reply — resume / poll an earlier ask or request_ackLook up whether you've replied to an earlier ask/request_ack — handy if the
blocking call timed out or your MCP client cancelled it. Pass the message_id
(and topic) it returned; non-blocking by default, or set wait_seconds to
briefly long-poll. Returns { responded, value?, replied_at? } (value is
"yes" / "no" / "ack"). Replies are kept ~30 minutes after the original
message was sent.
"Run the migration, and
send_alertme when it's done — priority 4 if it fails."
"If the nightly backup fails,
send_criticalme with the error — that one can't wait."
"Before you
DROPthe production table,askme to approve it — only proceed if I answer yes."
A concrete approval-gate flow:
Agent: about to delete the prod `events` table → calls
ask("Delete prod `events` table (12M rows)? This cannot be undone.")
… blocks; your phone buzzes …
You: tap "No"
Agent: ask returns { responded: true, approved: false, value: "no" } → aborts the deletion.
npm install
npm run build # → dist/index.js
npm test # vitest: unit (publish, config) + in-memory MCP integration
BLIPR_URL=https://blipr.dev BLIPR_TOPIC=demo node dist/index.js # stdio
MIT © Applogico LLC. This is the open client adapter; the Blipr server is distributed as a container image.
MCP server that lets AI agents send Blipr push alerts to your phone — your agent can page you.
{ "mcpServers": { "blipr-mcp": { "command": "npx", "args": [ "-y", "@blipr/[email protected]" ] } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
@blipr/mcp läuft lokal über stdio.
Zuletzt geprüft: 2026-11-14. MCP server that lets AI agents send Blipr push alerts to your phone — your agent can page you.