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.3210MIT
- AlicenseNot gradedqualityAmaintenanceEnables LLM agents to query and full-text search a local SQLite mirror of Telegram bot messages, chats, users, reactions, reply chains and stored file blobs, plus send, edit, pin and broadcast messages or ban, restrict and promote members. Without a bot token it returns action plans, while local reads and tool discovery work offline.1,347 npm1MIT
- 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.16 npm1ISC
- AlicenseNot gradedqualityBmaintenanceEnables agents to relay private Telegram messages with registered humans and other agents through a self-hosted, single-owner deployment. It supports bound Telegram bots, inbox acknowledgment flows, and optional routes for ChatGPT dot and xAI Grokbot.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and read locally stored chat history, look up contacts, send messages and attachments, and retrieve media through a self-hosted local daemon with encrypted SQLite storage.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access a self-hosted MAX messenger personal account: browse chats, read and search message history, inspect context, pins and forwarded text, download attachments, and send text or files with receipts and retry protection. Also supports durable batch state for scheduled workflows, with local authentication and access control over Streamable HTTP.MIT
TDQS
Scored across 13 tools
Most tools map to a distinct resource+action, but message retrieval is split across three tools (bot_get_new_messages for unread across all chats, bot_read_chat for one chat's recent history, bot_search_messages for text search), which could cause some misselection. Descriptions do a good job distinguishing them (unread vs. history vs. search, and which mark read), keeping overlap manageable.
Every tool follows a consistent bot_verb_noun snake_case pattern (bot_get_me, bot_send_message, bot_delete_message, bot_list_chats, bot_download_file). Verb choices are predictable (get/send/edit/delete/list/read/search/wait/download).
13 tools is well within the ideal 3-15 range and each tool earns its place in a messaging-bot workflow. Nothing feels padded or missing at the count level.
Covers the core messaging lifecycle well: send/edit/delete, read/search, wait-for-reply, file send/download, chat listing, chat info, and identity/webhook checks. Minor gaps exist—no tool to set/clear a webhook (only get_webhook_info), and no forward/pin or explicit button-keyboard send—but these are edge cases agents can largely work around.