What it does
End-to-end encrypted iPhone & Apple Watch approvals, code diffs, and live progress for AI agents.
- Connects 在你的电脑上运行
- Account or key No key needed
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 19/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 31/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 34 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 NotiBuddy。按照 https://mcp.popnx.com/i/yourbit-network-notibuddy.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月19日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
让 AI 帮你安装
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server NotiBuddy,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "notibuddy": { "command": "npx", "args": [ "-y", "notibuddy", "mcp", "--client", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 NotiBuddy 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 Node.js(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -v- 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
node -v安装一次,所有需要 Node.js 的工具都能用
打开电脑版 Claude 应用的设置文件
SettingsDeveloperEdit Config
粘贴这些设置并保存文件
{ "mcpServers": { "notibuddy": { "command": "npx", "args": [ "-y", "notibuddy", "mcp", "--client", "mcp" ] } } }退出 Claude 再重新打开
试一试
用 NotiBuddy 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 NotiBuddy,或回答中出现 NotiBuddy 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 NotiBuddy
NotiBuddy 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
你可以改用这些方式
A · 使用能连接 NotiBuddy 的应用
- 需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
- 需要先在电脑上安装 Node.js(只需一次)
- 需要先在电脑上安装 Node.js(只需一次)
- 需要先在电脑上安装 Node.js(只需一次)
B · 开发者工具 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
让 AI 帮你安装
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server NotiBuddy,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user notibuddy -- npx -y notibuddy mcp --client mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 NotiBuddy 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 Node.js(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -v- 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
node -v安装一次,所有需要 Node.js 的工具都能用
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --scope user notibuddy -- npx -y notibuddy mcp --client mcp在 Claude Code 中输入 /mcp
应能看到 NotiBuddy 在列表中并显示已连接
试一试
用 NotiBuddy 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 NotiBuddy,或回答中出现 NotiBuddy 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
让 AI 帮你安装
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server NotiBuddy,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "notibuddy": { "command": "npx", "args": [ "-y", "notibuddy", "mcp", "--client", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 NotiBuddy 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 Node.js(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -v- 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
node -v安装一次,所有需要 Node.js 的工具都能用
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 NotiBuddy 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 NotiBuddy,或回答中出现 NotiBuddy 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
让 AI 帮你安装
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server NotiBuddy,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "notibuddy": { "type": "stdio", "command": "npx", "args": [ "-y", "notibuddy", "mcp", "--client", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 NotiBuddy 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 Node.js(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -v- 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
node -v安装一次,所有需要 Node.js 的工具都能用
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 NotiBuddy 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 NotiBuddy,或回答中出现 NotiBuddy 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
开发者专用:终端命令和 JSON 设置
安装在电脑上
Claude Code
claude mcp add --scope user notibuddy -- npx -y notibuddy mcp --client mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"notibuddy": {
"command": "npx",
"args": [
"-y",
"notibuddy",
"mcp",
"--client",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"notibuddy": {
"command": "npx",
"args": [
"-y",
"notibuddy",
"mcp",
"--client",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"notibuddy": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"notibuddy",
"mcp",
"--client",
"mcp"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 yourbit-network 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于今天
- ✓ 通过
有许可证
使用 MIT
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
已公开的漏洞(OSV.dev)
尚未检查
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/yourbit-network-notibuddy)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6136 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 6136 个服务器的 99% 更新
- 基础检查结果等于或优于此分类中其他 6136 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
NotiBuddy 安全吗?
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于今天,最新版本(0.3.3)于今天进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 NotiBuddy | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
NotiBuddy (notibuddy-mcp)
End-to-end encrypted requests and signed replies between your agents, apps or scripts and your Apple devices.
The public CLI and MCP server from Yourbit, LLC, published on npm as notibuddy. This repository contains the computer client and protocol documentation. Support: contact@notibuddy.app.
🔒 Security & Cryptographic Invariants
NotiBuddy is designed so that neither the relay server nor Apple Push Notification service (APNs) can read prompts, choices, code, or user responses.
- HPKE (RFC 9180): Requests use
DHKEM(P-256, HKDF-SHA256)+AES-256-GCMfor the addressed device. The Apple app stores its separate encryption private key in Keychain; this is a software key, not a Secure Enclave key. - Device ECDSA signatures: Replies use P-256 signing keys. The Apple app uses the Secure Enclave when available and a Keychain-protected software key otherwise. A valid signature proves possession of the paired key; it does not attest hardware storage or user authentication. Protected requests have separate authentication rules.
- Out-of-Band Pairing: Public keys and device fingerprints are exchanged via out-of-band bundles (
nbpair1...) verified with HMAC-SHA256. - Content and metadata: The relay transports encrypted message/file bodies, but it can read routing identities, primitive types, timestamps, sizes, delivery status and usage metadata. APNs tokens and connection IP addresses are also visible to the services handling them. Encryption does not make the service anonymous or hide all metadata.
The CLI stores software signing, receiving and pending-reply keys under the private local ~/.notibuddy store. Unix permissions and Windows account ACLs protect those files; the package does not use a hardware keystore. Paired endpoints can read the content addressed to them and may retain their own copies.
Read the complete normative specification in PROTOCOL.md and the security policy.
🚀 Quick Start
Use the versioned npx commands below without a global installation. In later examples, nb is shorthand for npx -y notibuddy@^0.3.0, or the executable from a global installation of that version or a compatible newer release.
1. Pair with your iPhone
In the NotiBuddy iOS app, tap Connect → Add connection → Share Setup and copy the pairing string, then run pair and paste it at the prompt (or pipe it) so the secret never hits shell history:
npx notibuddy@^0.3.0 pair --to personal
or on macOS:
pbpaste | npx notibuddy@^0.3.0 pair --to personal
This validates the phone identity, registers an independent connection key for this destination, and saves it in ~/.notibuddy/destinations/personal.json. The destination name is a local alias.
If compatible NotiBuddy setup includes a one-use code, the first eligible sender can connect without another approval tap. Keep the phone app open and online; the command waits up to 45 seconds for confirmation (--wait 0 returns immediately, maximum 60 seconds). “Waiting for NotiBuddy” means pairing is still pending. Run the same command with the same destination name to retry using the saved keys. The temporary code is used in memory and is not saved in the destination file.
If Terminal says Phone approval required, open Connect, compare the full Sender Key ID, and approve the connection. This is the path for legacy setup and later new senders using the same setup. One manual approval can be pending: a newer request replaces the previous one. Pending approvals expire after 15 minutes. An unchanged approved sender stays connected without another prompt.
Keep the entire setup private: anyone holding an unused code can race to connect first. Codes last at most ten minutes; expired or canceled codes grant no automatic access, though valid ordinary pairing credentials can still request manual approval. Canceling a code does not disconnect an already approved sender. Use Connect to disconnect a sender you do not recognize.
Use npx notibuddy@^0.3.0 status to inspect the locally saved configuration. Confirm approval in the phone's Connect screen; the status command does not check approval with the relay.
Check the connection
Run nb doctor --to personal to check relay reachability, sender approval, request-protocol compatibility, and file-receive setup. Diagnostics omit credentials and private keys. The client proves possession of the selected sender key and reads only that sender's approval state. Existing saved destinations supply their public key automatically; no re-pairing is needed. New clients can check older relays through a bounded compatibility path, but authentication failures never trigger that fallback.
Library callers that construct NotiBuddyClient directly should include senderPub (the public P-256 signing point) in NotiBuddyConfig when calling doctor. A successful registerSender also supplies that point to the same client instance. The private signing key can remain nonextractable. If public identity is missing or mismatched, diagnostics remain unverified instead of using an unsigned lookup.
An unavailable or invalid response reports the sender as unverified; it does not mean the connection was removed. All checks share a 15-second timeout, including compatibility requests to older relays, and negotiated phone/Watch delivery is never downgraded by a diagnostics failure.
Ordinary interactive requests (approvals, protected approvals, text replies, forms, and diffs) remain answerable for three hours by default. Set a shorter lifetime with nb notify "Review release" --to personal --options "Approve,Reject" --timeout 1800, JavaScript timeoutSeconds, or MCP timeout_seconds; the supported range is 1–10,800 whole seconds. This is separate from --wait / wait_seconds, which controls how long one interactive call waits before returning pending (maximum 55 seconds). Resuming or retrying keeps the original signed expiry, even if a different timeout is supplied. Activities retain their existing one-hour lifetime and timer behavior.
If an interactive notify returns pending, keep its request ID and resume it with nb notify --resume --to personal. Network interruptions and invalid replies preserve this identity; avoid sending a second request for the same decision. A positive --wait is an overall operation budget. --wait 0 makes one bounded lookup. Interrupting an active interactive CLI notify prints its resume ID when it has already been saved.
The client supports explicitly negotiated phone/Watch group requests with a compatible app and relay. Pairings without that negotiation continue to use v1. Set up the Watch through the iPhone app; changing configuration fields manually does not enable a Watch app.
2. Test via CLI
When only one destination is paired, everyday CLI commands (notify, activity, files, doctor) auto-select it if --to is omitted.
# Send a one-way informational notification (no action buttons or waiting):
npx notibuddy@^0.3.0 notify "Build finished" --to personal --sender "Build monitor" --message "All checks passed."
Request approval with custom buttons:
npx notibuddy@^0.3.0 notify "Deploy v1.2 to production?" --to personal --sender "Deployment script" --options "Approve,Deny"
Require device-owner authentication (Face ID, Touch ID, passcode, or unlocked Watch):
npx notibuddy@^0.3.0 notify "Execute database migration?" --to personal --options "Proceed,Abort" --requires-auth
Start a countdown timer on the Dynamic Island:
npx notibuddy@^0.3.0 activity "sprint-1" start --to personal --title "Sprint Timer" --timer 25
Review a text change (0.2.1+)
Save a UTF-8 JSON file named changes.json:
{
"filename": "src/config.ts", "language": "typescript", "original": "const retries = 2;\n", "modified": "const retries = 3;\n" }
npx notibuddy@^0.3.0 notify "Review retry change" --to personal --diff changes.json --requires-auth --sensitive
The filename and source text are encrypted for the destination. Review happens on iPhone or iPad; a paired Watch hands off to its iPhone. The response uses approve (Apply) or reject (Discard). These are decisions: NotiBuddy does not change files or execute code. The caller must verify the current file still matches the reviewed original before applying an approved change.
For MCP, pass diff: {"filename":"src/config.ts","language":"typescript","original":"const retries = 2;\n","modified":"const retries = 3;\n"} to notibuddy_notify, together with title, requires_auth: true, sensitive: true, and to when using --allow-to. The library accepts the same diff object in client.ask(...).
filename is a display name, never a file to open on the recipient. language is optional. Empty original or modified text supports file creation or deletion. Source text is limited to a combined 96,000 UTF-8 bytes and 20,000 lines (each text starts at one line; each newline adds one). The CLI JSON file must be a regular file no larger than 150,000 bytes. The full encrypted request must also fit the protocol limit; JSON escaping and other fields can make a smaller diff too large. Invalid inputs fail before sending.
Do not combine a diff with choices, text input, forms, or a resume ID. If the result is pending, resume the returned ID without --diff or the MCP diff object. Source text may remain in the private pending-request store until dispatch is acknowledged, allowing the exact request to survive an interrupted send; the caller's input file remains their responsibility.
🛠️ Model Context Protocol (MCP) Setup
You can connect NotiBuddy directly to your favorite agent tools. Pairing prints an MCP configuration that pins the exact installed package version. When updating an existing configuration, change its package version to the release you installed (for example notibuddy@0.3.2) and restart the MCP server; preserve its destination and sender options. This version update does not require re-pairing or new keys.
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": { "notibuddy": { "command": "npx", "args": ["-y", "notibuddy@0.3.2", "mcp", "--to", "personal", "--sender", "Coding assistant"] } } }
Cursor / Antigravity / Claude Code
Run as a local stdio MCP server:
{
"mcpServers": { "notibuddy": { "command": "npx", "args": ["-y", "notibuddy@0.3.2", "mcp", "--to", "personal", "--sender", "Coding assistant"] } } }
Update notices
The CLI checks npm for a newer release at most once a day (an anonymous request to registry.npmjs.org) and prints a one-line notice on stderr; stdout and exit codes are unchanged. MCP sessions show the notice once, as an extra item in a tool result. Set NOTIBUDDY_NO_UPDATE_CHECK=1 to turn the check off.
🧪 Testing Test Vectors
Verify compliance with Protocol v1:
npm ci
npm run build npm test
Test vectors are located in test-vectors/v1.json.
Node.js 20 or newer is required. Tests use isolated local fixtures and do not need a phone, relay credentials, or access to another repository. Test-vector keys and pairing bundles are synthetic and are not usable production credentials.
Pre-push secret checks (contributors)
Contributions require the NotiBuddy Contributor Assignment Agreement, based on Harmony CAA 1.0. It assigns contribution