Skip to main content
Glama
signal-cli-mcp

signal-cli-mcp

by jiridudekusy

Related Servers

Alternatives to signal-cli-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables AI agents to pause and request human approval or information via Slack, Telegram, or macOS dialogs before proceeding with actions.
      2
      15
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that acts as an AI assumption firewall, intercepting risky decisions, detecting contradictions, and routing human approval requests via Telegram or Slack.
      8
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for AI agents to send notifications, copy to clipboard, request confirmations, and collect text input from users across their devices.
      10
      35 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides an MCP endpoint per AI agent that exposes tools to read new messages, post to a shared thread, and request human approval before acting outside it. People and their agents converse in one private, self-hosted chat where only human messages count as instructions and server-enforced reply, hand-off, and daily-post limits keep agent activity in check.
      3 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An 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
    • A
      license
      A
      quality
      D
      maintenance
      MCP 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.
      10
      13 npm
      1
      MIT

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    All tools follow a consistent 'propose[Action]' pattern with clear noun phrases (SignalMessage, SignalGroupMessage, SignalGroupCreation). The naming is uniform and predictable.

    Tool Count3/5

    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.

    Completeness2/5

    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.