D
dhyegocalota/zapbip
Your AI agents text you on WhatsApp.
★ 1·updated 2026-11-16
View on GitHub ↗Link checked 2026-11-17 · HTTP 200 · opens the vendor's own site
Official description💬 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
- Star count
- 1 ★ · dhyegocalota/zapbip · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-15 · last seen 2026-11-20 · seen 6× · listed by 1 sources
- Score
- score 103 · 1 ★ · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Open Source. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
dhyegocalota/zapbip;first catalogued 2026-11-15;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
zapbip
Excerpted from the repository README (abridged)
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.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/dhyegocalota-zapbip/)
- Source
- github · https://github.com/dhyegocalota/zapbip
- Browse by field
- Open source
- Traction
- 1 ★
- added
- today
More entries
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.