Signal MCP
Related Servers
Alternatives to Signal MCP
- FlicenseNot gradedqualityDmaintenanceMCP Server for retrieving Signal messages using signal-export logic.8-
- AlicenseAqualityAmaintenanceLocal Signal MCP server: read via Signal Desktop, send via signal-cli8MIT
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for Signal via signal-cli that enables sending and receiving messages, managing contacts and groups, and reacting over stdio.2 npm-
- AlicenseNot gradedqualityBmaintenanceMCP server that wraps a running signal-cli daemon's JSON-RPC API as MCP tools, enabling list contacts, groups, conversations, read and send messages, and react to messages on Signal.17 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCPL server that bridges Signal via signal-cli, exposing DMs and group chats as channels and providing signal_send and signal_react tools.Blue Oak Model 1.0.0
- AlicenseNot gradedqualityAmaintenanceMCP server for a local-first messaging workspace that integrates Google Messages, WhatsApp, and Signal. It enables reading, sending, searching messages, and managing conversations through MCP tools.55-
- AlicenseBqualityBmaintenanceAn 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
- FlicenseNot gradedqualityFmaintenanceAn MCP integration for signal-cli that allows AI agents to send and receive Signal messages, supporting direct messages, group messages, and async message handling.26-
TDQS
Scored across 79 tools
Tools are clearly distinguished by descriptions that explicitly separate DM vs group vs self variants and different receive methods. While there are many similar-sounding tools (e.g., receive_messages vs receive_direct vs get_unread), each has a distinct purpose and the descriptions provide unambiguous guidance.
All tool names follow a consistent verb_noun pattern (send_message, list_groups, update_profile, get_conversation). Even longer names like submit_rate_limit_challenge adhere to the pattern. There are no mixed conventions or chaotic variations.
With 79 tools, this is far beyond the typical well-scoped server (3-15). While each tool has a distinct purpose, the surface is enormous and could be consolidated (e.g., merging DM/group variants with a parameter). The sheer number makes it heavy and potentially overwhelming for agents.
The tool set covers virtually every aspect of Signal: messaging (text, attachments, stickers, polls, reactions, typing), groups, contacts, devices, profile, settings, local store management, scheduling, webhooks, security (PIN, identity), and number migration. No obvious gaps in the domain.