D
dhyegocalota/zapbip
Your AI agents text you on WhatsApp.
★ 1·更新 2026-11-16
在 GitHub 查看 ↗链接已于 2026-11-17 核查 · HTTP 200 · 打开的是厂商自己的官网
官方说明💬 Your AI agents text you on WhatsApp. They ask with buttons, wait for your tap, then keep working. 🤖 Claude Code, Codex, Cursor & any MCP agent · ✅ official WhatsApp Cloud API · 🔓 open source
- ★ 数取值
- 1 ★ · dhyegocalota/zapbip · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-11-15 · 最近见到 2026-11-20 · 共见到 6 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 1 ★ · 1 个来源 · repo
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
dhyegocalota/zapbip;我们收录于 2026-11-15;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
zapbip
以下摘录自该仓库的 README(片段)
Your AI agents text you on WhatsApp.
They ask with buttons, wait for your tap, then keep working.
Website ·
Docs ·
Quick start ·
Issues
Your usual AI, now on WhatsApp in five minutes, for what matters to you. Connect the AIs you already use, or any MCP client, to your own phone through one MCP server: they send you messages, ask questions with buttons or lists and wait for your answer, exchange files and voice notes, and wake up when you text first. Several agents share one chat, and each reply goes back to the agent that asked.
It uses only Meta's official WhatsApp Cloud API, it talks only to you, and it deletes each message after a fixed time.
## 🤔 Why this is not a full WhatsApp channel
A full channel moves the whole conversation into WhatsApp: the AI lives there, and everything it does goes through the chat. zapbip does the opposite. Your AI stays where it already works, with the same sessions, tools and habits, and picks zapbip up only when it needs you or when you tell it to: "text me when the build ends", "ask me before you deploy". WhatsApp is the way to reach you, not the place the work happens.
The agent decides, or you do. It texts you at the moments that matter, or because you asked.
Nothing to rebuild. It works out of the box with the AIs you already use and with any MCP client, with no plugin to write and no workflow to move.
Five minutes. Message zapbip, paste one line into your AI, and it connects itself.
zapbip is a product of Logic Bit, made in Brazil: logicbit.com.br
## ✨ Features
💬 Messages that reach you. An agent texts you when it finishes, fails or needs you.
🔘 Questions with buttons and lists. The agent blocks until you tap, then keeps working.
📎 Files and voice notes in both directions.
🔔 Wake on text. Message first and your coding agent's session resumes in seconds.
👥 Many agents, one chat. Each reply is routed back to the agent that asked.
🔒 Yours alone. Official Cloud API only, one owner per account, every message deleted after a fixed time.
🧩 Any MCP client. One server, one key per agent, set up in minutes.
## 🚀 Quick start
1. Message zapbip on WhatsApp. Open the start link at zapbip.com and send any message. It creates your account on the waitlist, and zapbip tells you in that chat when your access opens.
2. Ask for an agent. Once you are in, send new agent claude. zapbip answers with one line made for you.
3. Paste it into your AI. Your agent reads the instructions online, connects itself and texts you a first message.
The full walk-through, with one guide per agent, is at docs.zapbip.com.
## 🧠 How it works
your agent ──MCP──▶ zapbip (Cloudflare Worker) ──WhatsApp Cloud API──▶ your phone
▲ │ one Durable Object per account │
└──── your answer ◀──┴── routed to the agent that asked ◀── you tap ─┘
MCP server. One endpoint and one key per agent. The tools send a message, ask with buttons or a list and wait, send and receive media, and check the inbox.
Account inbox. A Durable Object per account holds the queue, the open questions and the routing, so a reply reaches the agent that asked even when several agents share the chat.
Wake. When you text first, the local connector resumes your coding agent's session in seconds; hosted agents pick the message up at their next check.
They ask with buttons, wait for your tap, then keep working.
Website ·
Docs ·
Quick start ·
Issues
Your usual AI, now on WhatsApp in five minutes, for what matters to you. Connect the AIs you already use, or any MCP client, to your own phone through one MCP server: they send you messages, ask questions with buttons or lists and wait for your answer, exchange files and voice notes, and wake up when you text first. Several agents share one chat, and each reply goes back to the agent that asked.
It uses only Meta's official WhatsApp Cloud API, it talks only to you, and it deletes each message after a fixed time.
## 🤔 Why this is not a full WhatsApp channel
A full channel moves the whole conversation into WhatsApp: the AI lives there, and everything it does goes through the chat. zapbip does the opposite. Your AI stays where it already works, with the same sessions, tools and habits, and picks zapbip up only when it needs you or when you tell it to: "text me when the build ends", "ask me before you deploy". WhatsApp is the way to reach you, not the place the work happens.
The agent decides, or you do. It texts you at the moments that matter, or because you asked.
Nothing to rebuild. It works out of the box with the AIs you already use and with any MCP client, with no plugin to write and no workflow to move.
Five minutes. Message zapbip, paste one line into your AI, and it connects itself.
zapbip is a product of Logic Bit, made in Brazil: logicbit.com.br
## ✨ Features
💬 Messages that reach you. An agent texts you when it finishes, fails or needs you.
🔘 Questions with buttons and lists. The agent blocks until you tap, then keeps working.
📎 Files and voice notes in both directions.
🔔 Wake on text. Message first and your coding agent's session resumes in seconds.
👥 Many agents, one chat. Each reply is routed back to the agent that asked.
🔒 Yours alone. Official Cloud API only, one owner per account, every message deleted after a fixed time.
🧩 Any MCP client. One server, one key per agent, set up in minutes.
## 🚀 Quick start
1. Message zapbip on WhatsApp. Open the start link at zapbip.com and send any message. It creates your account on the waitlist, and zapbip tells you in that chat when your access opens.
2. Ask for an agent. Once you are in, send new agent claude. zapbip answers with one line made for you.
3. Paste it into your AI. Your agent reads the instructions online, connects itself and texts you a first message.
The full walk-through, with one guide per agent, is at docs.zapbip.com.
## 🧠 How it works
your agent ──MCP──▶ zapbip (Cloudflare Worker) ──WhatsApp Cloud API──▶ your phone
▲ │ one Durable Object per account │
└──── your answer ◀──┴── routed to the agent that asked ◀── you tap ─┘
MCP server. One endpoint and one key per agent. The tools send a message, ask with buttons or a list and wait, send and receive media, and check the inbox.
Account inbox. A Durable Object per account holds the queue, the open questions and the routing, so a reply reaches the agent that asked even when several agents share the chat.
Wake. When you text first, the local connector resumes your coding agent's session in seconds; hosted agents pick the message up at their next check.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/dhyegocalota-zapbip/)
- 来源
- github · https://github.com/dhyegocalota/zapbip
- 按领域浏览
- 开源项目
- Traction
- 1 ★
- 收录于
- 今天
更多条目
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。