SSyncDev

Signal Messaging (via signal-cli) MCP Server

Send Signal messages and read replies through your own signal-cli JSON-RPC daemon (unofficial).

Local serverstdio

What is the Signal Messaging (via signal-cli) MCP Server?

Signal Messaging (via signal-cli) is an MCP integration. Send Signal messages and read replies through your own signal-cli JSON-RPC daemon (unofficial).

Packages and local setup

The published oci package is ghcr.io/joshuawowk/signal-mcp:1.0.1. Its declared MCP transport is stdio.

The package declares SIGNAL_SENDER (required): E.164 number of the account registered in signal-cli (e.g. +15555550100); SIGNAL_DEFAULT_RECIPIENT (required): E.164 number messaged by default; tools accept a per-call recipient override; SIGNAL_RPC_URL: signal-cli HTTP JSON-RPC endpoint as seen from the container. The server's built-in default is http://127.0.0.1:8080/api/v1/rpc (use with --network host on Linux); this listing defaults to the Docker host alias.; SIGNAL_TCP_HOST: signal-cli daemon TCP host, used only for the receive-path health check; SIGNAL_TCP_PORT: signal-cli daemon TCP port (daemon started with --tcp), used only for the receive-path health check; SIGNAL_INBOX_PATH: Path of the replies inbox file inside the container (populated only by the subscriber process); SIGNAL_POLL_INTERVAL: Subscriber poll cadence in seconds; SIGNAL_INBOX_RETENTION_DAYS: Days of replies kept in the inbox file.

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 1.0.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related communication MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
SIGNAL_SENDERE.164 number of the account registered in signal-cli (e.g. +15555550100)Yes
SIGNAL_DEFAULT_RECIPIENTE.164 number messaged by default; tools accept a per-call recipient overrideYes
SIGNAL_RPC_URLsignal-cli HTTP JSON-RPC endpoint as seen from the container. The server's built-in default is http://127.0.0.1:8080/api/v1/rpc (use with --network host on Linux); this listing defaults to the Docker host alias.Check documentation
SIGNAL_TCP_HOSTsignal-cli daemon TCP host, used only for the receive-path health checkCheck documentation
SIGNAL_TCP_PORTsignal-cli daemon TCP port (daemon started with --tcp), used only for the receive-path health checkCheck documentation
SIGNAL_INBOX_PATHPath of the replies inbox file inside the container (populated only by the subscriber process)Check documentation
SIGNAL_POLL_INTERVALSubscriber poll cadence in secondsCheck documentation
SIGNAL_INBOX_RETENTION_DAYSDays of replies kept in the inbox fileCheck documentation