I-Bot MCP
OfficialRelated Servers
Alternatives to I-Bot MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides Claude Code read-only access to WhatsApp chats by mirroring them into a local SQLite database, allowing search, message listing, media retrieval, and optional voice-note transcription without any send capability.MIT
- AlicenseNot gradedqualityBmaintenanceProvides Claude with read-only access to your WhatsApp chat history entirely on your local machine, enabling natural language search, summarization, and retrieval of messages without sending data to the cloud.7 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to read, search, and reply to your personal WhatsApp messages by linking as an extra device, with support for chat history, full-text search, media downloads, and sending messages or files.28 npmMIT
- AlicenseAqualityDmaintenanceEnables Claude to read and search WhatsApp messages, transcribe voice notes, and analyze images locally through a read-only bridge.19MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to interact with WhatsApp: read chats, search messages, send messages with a mandatory confirmation step, and transcribe voice notes locally, all with encrypted storage and prompt-injection scrubbing.MIT
- AlicenseAqualityAmaintenanceEnables Claude Desktop to read, search, send, and broadcast WhatsApp messages and files, and manage groups and communities through a linked personal WhatsApp account.22MIT
TDQS
Scored across 9 tools
Each tool maps to a distinct target: message status, chat status, chat lookup, batch lookup, message history, media download, chat listing, custom fields, and tags. The only mild overlap is ibot_get_chat_status vs ibot_get_chat_link (both keyed on a chat) and get_chat_link vs its batch sibling, but the descriptions clearly separate them (status of a registration vs resolving a phone number to a chat_id/link).
All nine tools use the same ibot_ prefix plus a consistent snake_case verb_noun pattern (get_chat_status, read_messages, list_chats, download_media). The verb choice is semantically appropriate in each case (get/read/list/batch) rather than arbitrary, with no style mixing.
Nine tools is well within the ideal 3-15 range and each one covers a distinct capability of the panel (chats, messages, media, tags, fields, status, lookup, bulk lookup). Nothing appears redundant or padded.
The read surface is thorough: chats, message history (including internal notes), media, tags, custom fields, delivery and registration status, plus a batch variant for lookups. However the set is entirely read-only — there is no send-message, tag/custom-field write, archive, or mark-as-read operation, which is a notable gap for a WhatsApp bot panel (ibot_get_chat_link explicitly notes it does not send messages, implying no send tool exists).