bale-mcp
Related Servers
Alternatives to bale-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables LLMs to authenticate with a Bale Messenger account and then inspect dialogs, read chat histories, send/edit/forward messages, and manage contacts, groups, channels, reactions, and presence. Supports multiple locally stored account sessions with interactive SMS/2FA login.327MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with your personal WhatsApp account to search messages, list chats, and send messages. It stores all authentication and message data locally using SQLite for privacy and direct multi-device API connection.5 npm1ISC
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read WhatsApp chat history from a SQLite archive, optionally scrape live chats, and send messages through a chain of safety guards.26 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with your personal WhatsApp account, allowing them to search messages and contacts, retrieve chat history, and send messages to individuals or groups. Uses WhatsApp Web API with local data storage for privacy and security.5 npmISC
- AlicenseBqualityCmaintenanceLets coding agents browse a personal Telegram account locally, retrieving per-chat text history and conversations or outgoing messages by date via QR login, read-only unless message sending is explicitly enabled. API credentials from Telegram are required, and access can be restricted to specific numeric chat IDs.3MIT
- AlicenseAqualityBmaintenanceConnect any AI agent to your personal Telegram messages through the official Business API, enabling message history search and draft replies with optional manual approval.718MIT
TDQS
Scored across 13 tools
Most tools target clearly distinct actions (identity, chats, sending, editing, deleting, searching). The main overlap is between bot_get_new_messages (incremental cross-chat poll) and bot_read_chat (per-chat history), both of which retrieve messages and mark them read, but the descriptions distinguish them reasonably well.
Every tool follows a predictable bot_verb_noun pattern (bot_send_message, bot_edit_message, bot_download_file, etc.) with a consistent bot_ prefix. bot_get_me is the only mild deviation but still fits the verb_noun shape.
13 tools sit comfortably in the well-scoped range and each covers a distinct capability (send text/file, edit, delete, read, search, wait, download, chat metadata). Nothing feels redundant or padded.
Core bot workflows are covered: identity, chats, message send/edit/delete, reading, searching, waiting for replies, and file download. The notable gap is webhook management (only bot_get_webhook_info exists, no set/delete), which the descriptions imply matters since reading fails while a webhook is set.