# Signal Messaging (via signal-cli)

> Signal Messaging (via signal-cli) is an open-source MCP server for communication. Send Signal messages, questions and permission requests, and read replies, via signal-cli. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** self-hosted, CLI, Linux
- **Repository:** https://github.com/joshuawowk/signal-mcp
- **MCP Registry name:** io.github.joshuawowk/signal-mcp
- **Categories:** [communication](https://ai-powered.com/categories/communication)
- **Listing updated:** 2026-11-18

## About

This is an unofficial bridge for people who want an agent to message them on Signal when a task finishes or when it is stuck. It does not register numbers, run the daemon or talk to Signal's servers; it is purely a client of your own signal-cli JSON-RPC daemon, and the Signal identity keys never enter the container.

The design uses two channels. Sends and health checks go over the daemon's HTTP endpoint, while incoming replies stream over a TCP socket into an inbox file read by an optional subscriber process, because the HTTP receive method is locked by signal-cli's own auto-receive loop. A standalone stdio container has no subscriber, so replies are only collected in the Docker Compose deployment. Replies are kept for 14 days by default.

Five tools are listed: send a message, send a question with optional answer choices, send a permission request before an irreversible action, check replies by session, and a health check. Requirements are a running signal-cli daemon, a registered Signal number and Docker. The README warns that the daemon's HTTP endpoint is unauthenticated and should not be exposed beyond a trusted interface. The project says it is not affiliated with Signal.

## Features

- **Send messages:** Sends task-done pings and updates to a default or chosen recipient.
- **Ask questions:** Sends a blocking question with optional answer choices.
- **Permission requests:** Asks for an explicit yes before an irreversible action.
- **Reply polling:** Reads replies, filterable by session ID.
- **Health check:** Reports send path, receive path and inbox status.
- **Docker deployment:** Runs as a container using the host's signal-cli daemon.

## Good for

- Get a phone ping when a long agent task finishes
- Let an agent ask you a question while you are away
- Require a yes from your phone before a risky action
- Check that your Signal bridge is working

## Install

### Claude Code (Terminal)

```sh
claude mcp add signal-mcp --env SIGNAL_SENDER='<SIGNAL_SENDER>' --env SIGNAL_DEFAULT_RECIPIENT='<SIGNAL_DEFAULT_RECIPIENT>' -- docker run -i --rm -e SIGNAL_SENDER -e SIGNAL_DEFAULT_RECIPIENT ghcr.io/joshuawowk/signal-mcp:1.0.1
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "signal-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "SIGNAL_SENDER",
        "-e",
        "SIGNAL_DEFAULT_RECIPIENT",
        "ghcr.io/joshuawowk/signal-mcp:1.0.1"
      ],
      "env": {
        "SIGNAL_SENDER": "<SIGNAL_SENDER>",
        "SIGNAL_DEFAULT_RECIPIENT": "<SIGNAL_DEFAULT_RECIPIENT>"
      }
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "signal-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "SIGNAL_SENDER",
        "-e",
        "SIGNAL_DEFAULT_RECIPIENT",
        "ghcr.io/joshuawowk/signal-mcp:1.0.1"
      ],
      "env": {
        "SIGNAL_SENDER": "<SIGNAL_SENDER>",
        "SIGNAL_DEFAULT_RECIPIENT": "<SIGNAL_DEFAULT_RECIPIENT>"
      }
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "signal-mcp": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "SIGNAL_SENDER",
        "-e",
        "SIGNAL_DEFAULT_RECIPIENT",
        "ghcr.io/joshuawowk/signal-mcp:1.0.1"
      ],
      "env": {
        "SIGNAL_SENDER": "<SIGNAL_SENDER>",
        "SIGNAL_DEFAULT_RECIPIENT": "<SIGNAL_DEFAULT_RECIPIENT>"
      }
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "signal-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "SIGNAL_SENDER",
        "-e",
        "SIGNAL_DEFAULT_RECIPIENT",
        "ghcr.io/joshuawowk/signal-mcp:1.0.1"
      ],
      "env": {
        "SIGNAL_SENDER": "<SIGNAL_SENDER>",
        "SIGNAL_DEFAULT_RECIPIENT": "<SIGNAL_DEFAULT_RECIPIENT>"
      }
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "signal-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "SIGNAL_SENDER",
        "-e",
        "SIGNAL_DEFAULT_RECIPIENT",
        "ghcr.io/joshuawowk/signal-mcp:1.0.1"
      ],
      "env": {
        "SIGNAL_SENDER": "<SIGNAL_SENDER>",
        "SIGNAL_DEFAULT_RECIPIENT": "<SIGNAL_DEFAULT_RECIPIENT>"
      }
    }
  }
}
```

## Tools

- `signal_send_message`: Send a task-done ping or update with no reply expected
- `signal_send_question`: Send a question with optional answer choices
- `signal_send_permission_request`: Ask for explicit approval before an irreversible action
- `signal_check_replies`: Poll for replies, optionally filtered by session
- `signal_health`: Report health of the send path, receive path and inbox

## FAQ

### What do I need first?

A running signal-cli JSON-RPC daemon and a Signal number already registered with it.

### Can it receive replies?

Yes, in the Compose deployment with the subscriber and the daemon's TCP stream. A standalone stdio container is send-only.

### Is it official?

No. It is unofficial and not affiliated with Signal Messenger or the Signal Foundation.

### How long are replies kept?

14 days by default, set by SIGNAL_INBOX_RETENTION_DAYS.

### Is Signal Messaging (via signal-cli) free?

Yes. Signal Messaging (via signal-cli) is open source, so you can use and self-host it for free.

### How do I add Signal Messaging (via signal-cli) to Claude Code?

Run this command in your terminal: claude mcp add signal-mcp --env SIGNAL_SENDER='<SIGNAL_SENDER>' --env SIGNAL_DEFAULT_RECIPIENT='<SIGNAL_DEFAULT_RECIPIENT>' -- docker run -i --rm -e SIGNAL_SENDER -e SIGNAL_DEFAULT_RECIPIENT ghcr.io/joshuawowk/signal-mcp:1.0.1

### What are the best alternatives to Signal Messaging (via signal-cli)?

The closest alternatives to Signal Messaging (via signal-cli) are TrendRadar, Getmitra, Discord, Zoom and Email Spam Tester.

## Where this comes from

- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.

## Alternatives

- [TrendRadar](https://ai-powered.com/mcp/trendradar): TrendRadar is an open-source MCP server for communication.
- [Getmitra](https://ai-powered.com/mcp/getmitra): Getmitra is an MCP server for communication.
- [Discord](https://ai-powered.com/mcp/discord-2): Discord is a freemium MCP server for communication.
- [Zoom](https://ai-powered.com/mcp/zoom): Zoom is a freemium MCP server for communication.
- [Email Spam Tester](https://ai-powered.com/mcp/email-spam-tester): Email Spam Tester is a free MCP server for communication.
- [Slack_connect](https://ai-powered.com/mcp/slack-connect): Slack_connect is a freemium MCP server for communication.
- [Postmark](https://ai-powered.com/mcp/postmark): Postmark is a freemium MCP server for communication.
- [Gmail](https://ai-powered.com/mcp/gmail-5): Gmail is a freemium MCP server for communication.

---
Source: https://ai-powered.com/mcp/signal-messaging-via-signal-cli
