Send Signal messages and read replies through your own signal-cli JSON-RPC daemon (unofficial).
Signal Messaging (via signal-cli) is an MCP integration. Send Signal messages and read replies through your own signal-cli JSON-RPC daemon (unofficial).
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.
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.
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.
| Variable | Description | Required |
|---|---|---|
| SIGNAL_SENDER | E.164 number of the account registered in signal-cli (e.g. +15555550100) | Yes |
| SIGNAL_DEFAULT_RECIPIENT | E.164 number messaged by default; tools accept a per-call recipient override | Yes |
| 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. | Check documentation |
| SIGNAL_TCP_HOST | signal-cli daemon TCP host, used only for the receive-path health check | Check documentation |
| SIGNAL_TCP_PORT | signal-cli daemon TCP port (daemon started with --tcp), used only for the receive-path health check | Check documentation |
| SIGNAL_INBOX_PATH | Path of the replies inbox file inside the container (populated only by the subscriber process) | Check documentation |
| SIGNAL_POLL_INTERVAL | Subscriber poll cadence in seconds | Check documentation |
| SIGNAL_INBOX_RETENTION_DAYS | Days of replies kept in the inbox file | Check documentation |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
AI resume triage for recruiters. Query your candidate pool from Claude or ChatGPT.
<details> <summary><strong>Sister projects from n24q02m</strong> (click to expand)</summary>
Feishu/Lark OpenAPI MCP
Turn every meeting you have ever had into searchable context for your assistant