signal-cli-mcp
Related Servers
Alternatives to signal-cli-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAn MCP server that enables AI agents to pause and request human approval or information via Slack, Telegram, or macOS dialogs before proceeding with actions.215Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that acts as an AI assumption firewall, intercepting risky decisions, detecting contradictions, and routing human approval requests via Telegram or Slack.81MIT
- AlicenseAqualityBmaintenanceMCP server for AI agents to send notifications, copy to clipboard, request confirmations, and collect text input from users across their devices.11623 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI assistants read-only access to your personal Telegram account via MTProto, enforcing a whitelist of allowed chats and never marking messages as read.MIT
- AlicenseAqualityBmaintenanceMCP server that gives an AI assistant simultaneous access to multiple Gmail accounts with per-account read-only, draft, or send tiers, two-phase write confirmation, and safeguards for handling untrusted email content.107 npmMIT
- AlicenseAqualityAmaintenanceAn MCP server that gives AI agents permission-gated, audit-logged access to private email providers (Proton Mail via Bridge and plain IMAP), running locally with OAuth-based authentication and human-controlled escalation for destructive operations.66130 npm11MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: sending to an individual, sending to a group, and creating a group. The recipient type and action are explicit in the names, leaving no ambiguity.
All tools follow a consistent 'propose[Action]' pattern with clear noun phrases (SignalMessage, SignalGroupMessage, SignalGroupCreation). The naming is uniform and predictable.
At 3 tools, the count is at the low end of the typical range. While each tool earns its place, the server feels minimal and could benefit from a few more operations to feel well-rounded.
The server covers sending messages and creating groups but lacks any receive, list, or management capabilities. For a Signal client, this is a significant gap that would prevent agents from performing common workflows.