Text and read iMessages with Claude, Gmail-style: human-in-the-loop, no auto-replies. Ships an iMessage MCP server over the imsg engine (sendmessage with iMessage/SMS auto-routing, listchats, readmessages, searchmessages, react, watch) plus skills for sending, reading, listening, and one-time setup. macOS only.
MCP server "imessage" as configured in bowlofarugula/texting. Launched with /bin/sh -c BUN="$(command -v bun || echo "$HOME/.bun/bin/bun")"; exec "$BUN" run.
Watch for new iMessages from a contact while this session is open — "listen for messages from Sam", "let me know when Alex replies". Polls on a timer, surfaces new messages, drafts (never auto-sends) replies. Use when the user wants to be told about incoming texts, not for one-off reads (use texting-messages) or 24/7…
Read iMessages — "any new messages from Sam?", "what did Sarah say?", "catch me up on my texts". Resolves contact names to handles and reads conversation history via the readmessages tool.
Send an iMessage to someone from this session. Use when the user asks to text someone, send a message, iMessage a person, or "tell X" something over text. Works on macOS; Claude confirms the exact text before sending.
One-time setup for texting over iMessage from Claude — installs the imsg engine and walks the Full Disk Access + Automation grants. Use when the user asks to set up texting, when the iMessage tools (sendmessage/readmessages) are missing or erroring, or before the first send/read on a new Mac.
Check that texting over iMessage is healthy — imsg engine installed, Messages database readable, tools live. Use when the user asks whether texting works, why a send/read failed, or who Claude can text.
Send and read WhatsApp messages with Claude, Gmail-style: human-in-the-loop, no auto-replies. Ships a WhatsApp MCP server over the wacli engine (authenticate, sendmessage, listchats, readmessages, searchmessages, react, watch, status, plus contacts/groups helpers) and skills for sending, reading, listening, and one.
MCP server "whatsapp" as configured in bowlofarugula/whatsapp. Launched with /bin/sh -c BUN="$(command -v bun || echo "$HOME/.bun/bin/bun")"; exec "$BUN" run.
0 2mo agoA
tokens not measured
copy · 89%Apache-2.0
Watch for new WhatsApp messages from a contact while this session is open — "listen for WhatsApp messages from Sam", "let me know when Alex replies on WhatsApp". Polls on a timer, surfaces new messages, drafts (never auto-sends) replies. Use when the user wants to be told about incoming messages, not for one-off reads…
Read WhatsApp messages — "any new WhatsApp messages from Sam?", "what did Sarah say on WhatsApp?", "catch me up on my WhatsApp". Resolves names to chats and reads conversation history via the readmessages tool.
Send a WhatsApp message to someone from this session. Use when the user asks to WhatsApp someone, send a WhatsApp message, message a person on WhatsApp, or "tell X" something over WhatsApp. Claude confirms the exact text before sending.
One-time setup for WhatsApp from Claude — installs the wacli engine (official release download, checksum-verified) and links the device by scanning an in-chat QR (or entering a pairing code), no terminal, via the authenticate tool, then the initial sync. Use when the user asks to set up WhatsApp, when the WhatsApp…
Check that WhatsApp from Claude is healthy — wacli engine installed, device linked, local store reachable, tools live. Use when the user asks whether WhatsApp works, why a send/read failed, or who Claude can message.