Signal Messaging (via signal-cli)

io.github.joshuawowk/signal-mcp

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

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Claude Desktop · Cursor.

{
  "mcpServers": {
    "signal-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/joshuawowk/signal-mcp:1.0.1"
      ],
      "env": {
        "SIGNAL_SENDER": "<your SIGNAL_SENDER>",
        "SIGNAL_DEFAULT_RECIPIENT": "<your SIGNAL_DEFAULT_RECIPIENT>",
        "SIGNAL_RPC_URL": "http://host.docker.internal:8080/api/v1/rpc",
        "SIGNAL_TCP_HOST": "127.0.0.1",
        "SIGNAL_TCP_PORT": "7583",
        "SIGNAL_INBOX_PATH": "/data/inbox.jsonl",
        "SIGNAL_POLL_INTERVAL": "3",
        "SIGNAL_INBOX_RETENTION_DAYS": "14"
      }
    }
  }
}
Environment variables
  • SIGNAL_SENDERrequiredE.164 number of the account registered in signal-cli (e.g. +15555550100)
  • SIGNAL_DEFAULT_RECIPIENTrequiredE.164 number messaged by default; tools accept a per-call recipient override
  • 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.
  • SIGNAL_TCP_HOSTsignal-cli daemon TCP host, used only for the receive-path health check
  • SIGNAL_TCP_PORTsignal-cli daemon TCP port (daemon started with --tcp), used only for the receive-path health check
  • SIGNAL_INBOX_PATHPath of the replies inbox file inside the container (populated only by the subscriber process)
  • SIGNAL_POLL_INTERVALSubscriber poll cadence in seconds
  • SIGNAL_INBOX_RETENTION_DAYSDays of replies kept in the inbox file

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
1.0.1
Registry
active
Published
10/20/2026
Browse all Developer Tools →

Add the badge to your site

Show visitors that Signal Messaging (via signal-cli) is listed here — it’s also the link we check for a free listing.

Signal Messaging (via signal-cli) — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-joshuawowk-signal-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Signal Messaging (via signal-cli) — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Signal Messaging (via signal-cli) — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-joshuawowk-signal-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.