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-cli9MIT
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for Signal via signal-cli that enables sending and receiving messages, managing contacts and groups, and reacting over stdio.15 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 gradedqualityCmaintenanceMCPL 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 gradedqualityBmaintenanceMCP 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.66-
- 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 81 tools
Each tool's description is exceptionally cross-referenced, but the surface is crowded with near-parallel variants that could be confused: send_message / send_group_message / send_attachment / send_group_attachment / send_note_to_self / send_sticker / send_group_sticker all mean 'send something', and delete_message / delete_group_message / admin_delete_message / delete_local_messages / clear_local_store / prune_store form a dense deletion cluster. The receive trio (receive_messages / receive_direct / get_unread) and the set_expiration_timer vs update_group(expiration_seconds) overlap add further selection burden. Boundaries are documented, but the agent must read carefully to pick correctly.
Names follow a strictly consistent snake_case verb_noun pattern (list_contacts, send_group_message, update_group, terminate_poll, remove_device, prune_store). Read and write operations are clearly signaled by their verb prefixes throughout all 81 tools with no mixed conventions.
81 tools is far beyond a comfortable surface for an agent. While the domain is genuinely broad (messaging, groups, devices, account, stickers, polls, stories, scheduling, local store), many tools are one-shot admin operations (set_pin, submit_rate_limit_challenge, finish_change_number, upload_sticker_pack) or parameterizable variants that could be collapsed, making the set heavy and hard to navigate.
Coverage is exhaustive: full messaging lifecycle (send/edit/react/pin/delete/read-receipt), group and membership administration, contacts, profiles, devices, identity/trust, polls, stories, stickers, scheduling, and local-store import/export/prune management. There are essentially no dead ends for the stated purpose of controlling a full Signal account.