xmpp-mcp
Related Servers
Alternatives to xmpp-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA least-privilege, send-only MCP server for WhatsApp, backed by Meta's official WhatsApp Cloud API. It exposes tools to send text messages and pre-approved templates.12 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to work with the official Meta WhatsApp Business Cloud API: it ingests signed webhook events into SQLite, lists and reads stored conversations, searches message history, and prepares text or template messages with an explicit two-step human confirmation before a single send attempt. It also reports status and capabilities without exposing secrets.-
- AlicenseNot gradedqualityCmaintenanceEnables a single owner to run an authenticated Streamable HTTP MCP endpoint backed by their own BotFather token, with tools to check bot status, poll allowlisted updates, inspect and acknowledge pending messages, and optionally send replies when explicitly enabled. It supports safe disconnected startup and avoids private-account sessions, multi-user services, schedulers, or automatic retries.MIT
- AlicenseBqualityCmaintenanceAn MCP server that enables interaction with WhatsApp using the Baileys library and Streamable HTTP transport. It supports managing contacts, chats, and messages, while providing a web admin UI for QR code authentication and media handling.285MIT
- AlicenseNot gradedqualityBmaintenanceExposes each authenticated WhatsApp Web session on a Windows PC as a stateless Streamable HTTP MCP endpoint, letting MCP clients list chats, read and search messages, fetch profiles, and send text messages under per-session read-only or read-and-send permissions.MIT
- FlicenseNot gradedqualityAmaintenanceRuns a plain stdio MCP server that lets a Claude Code session send and receive chat messages from a linked phone number or official business account, including media, voice-note transcription, chunked long replies, and @-mentions. Inbound messages can wake the session, and gated access through pairing codes, allowlists and group policies lets only trusted contacts reach it, with tool-permission prompts approvable remotely by emoji reaction.-
TDQS
Scored across 5 tools
Each tool targets a distinct action: status check, send, set chat state, poll, and wait. Poll and wait are differentiated by blocking behavior, so there is no ambiguity.
All tools share an xmpp_ prefix and mostly follow a verb_noun pattern (send_message, set_chat_state, poll_messages, wait_for_message). The one exception is xmpp_status, which is a noun phrase rather than a verb_noun, a minor deviation.
With 5 tools, the server is well-scoped for its focused purpose of interacting with a single XMPP connection. Each tool earns its place, and the count is within the ideal 3-15 range.
The tool set covers the essential lifecycle for an XMPP connection: check status, send messages, publish chat state, and retrieve messages via poll or wait. No obvious gaps exist for the stated domain of a restricted single-recipient XMPP connection.