Skip to main content
Glama
Sealjay

mcp-signal

by Sealjay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-signal

No user-submitted related servers found.

    Related Servers

    • signal-mcp

      daanrongen
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Signal via signal-cli that enables sending and receiving messages, managing contacts and groups, and reacting over stdio.
      11 npm
      -

    • signal-mcp-server

      Transmitt0r
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP 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 npm
      MIT

    • openmessage

      MaxGhenis
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP 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.
      64
      -

    • signal-mcp-remote

      febin-micheal
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables remote Model Context Protocol clients to securely read, search, and send Signal Messenger messages through an HTTP interface backed by a personal signal-cli daemon.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target clearly distinct operations, especially read/search/send/decrypt. The main overlap is among list_chats, list_groups, and chat_activity, but descriptions explicitly differentiate their purposes (combined directory, group_id lookup, activity ranking).

    Naming Consistency4/5

    The tool set uses consistent snake_case and mostly follows a verb_noun or noun_status pattern. pairing_status and chat_activity deviate slightly from the dominant verb_noun convention, but remain readable and predictable.

    Tool Count5/5

    Nine tools is well-scoped for a Signal integration covering setup, discovery, reading, searching, attachment decryption, and sending. Each tool appears to earn its place without obvious redundancy.

    Completeness4/5

    The surface covers the core Signal lifecycle: status, pairing, chat/group discovery, message reading/searching, attachment decryption, and sending. Minor gaps exist around sending attachments, reactions, or deletion, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources