What it does
Send Signal messages and read replies through your own signal-cli JSON-RPC daemon (unofficial).
- Connects Runs on your computer
- Account or key No key needed · 2 settings to fill in (SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT)
- Category Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 7/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Signal Messaging (via signal-cli). Follow https://mcp.popnx.com/i/joshuawowk-signal-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
2 setting(s) to fill in (SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT) · Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Let AI install it
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Signal Messaging (via signal-cli) for Claude on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "signal": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "SIGNAL_SENDER", "-e", "SIGNAL_DEFAULT_RECIPIENT", "ghcr.io/joshuawowk/signal-mcp:1.0.1", "python3", "/app/server.py" ], "env": { "SIGNAL_SENDER": "your-value", "SIGNAL_DEFAULT_RECIPIENT": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Signal Messaging (via signal-cli) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Docker (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
docker --version- A version number such as Docker version … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
docker --versionInstall once; it works for everything that needs Docker
Fill in 2 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
SIGNAL_SENDERE.164 number of the account registered in signal-cli (e.g. +15555550100)SIGNAL_DEFAULT_RECIPIENTE.164 number messaged by default; tools accept a per-call recipient override
Descriptions are as written by the maker.
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Paste these settings and save the file
{ "mcpServers": { "signal": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "SIGNAL_SENDER", "-e", "SIGNAL_DEFAULT_RECIPIENT", "ghcr.io/joshuawowk/signal-mcp:1.0.1", "python3", "/app/server.py" ], "env": { "SIGNAL_SENDER": "your-value", "SIGNAL_DEFAULT_RECIPIENT": "your-value" } } } }Quit Claude and open it again
Try it
Use Signal Messaging (via signal-cli) and tell me what you can do for me, then show me one thing✓ If Claude says it is using Signal Messaging (via signal-cli) or shows a Signal Messaging (via signal-cli) tool in the answer, you are connected
6 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
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… · default http://host.docker.internal:8080/api/v1/rpcSIGNAL_TCP_HOSTsignal-cli daemon TCP host, used only for the receive-path health check · default 127.0.0.1SIGNAL_TCP_PORTsignal-cli daemon TCP port (daemon started with --tcp), used only for the receive-path health check · default 7583SIGNAL_INBOX_PATHPath of the replies inbox file inside the container (populated only by the subscriber process) · default /data/inbox.jsonlSIGNAL_POLL_INTERVALSubscriber poll cadence in seconds · default 3SIGNAL_INBOX_RETENTION_DAYSDays of replies kept in the inbox file · default 14
Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Signal Messaging (via signal-cli) yet
Signal Messaging (via signal-cli) runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect Signal Messaging (via signal-cli)
- 2 setting(s) to fill in (SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT) · Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
- 2 setting(s) to fill in (SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT) · Install Docker on your computer first (one time)
- 2 setting(s) to fill in (SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT) · Install Docker on your computer first (one time)
- 2 setting(s) to fill in (SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT) · Install Docker on your computer first (one time)
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Works with Claude Code, with some setup first
2 setting(s) to fill in (SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT) · Install Docker on your computer first (one time)
Let AI install it
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Signal Messaging (via signal-cli) for Claude Code on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user signal --env SIGNAL_SENDER=your-value --env SIGNAL_DEFAULT_RECIPIENT=your-value -- docker run -i --rm -e SIGNAL_SENDER -e SIGNAL_DEFAULT_RECIPIENT ghcr.io/joshuawowk/signal-mcp:1.0.1 python3 /app/server.py 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Signal Messaging (via signal-cli) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Docker (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
docker --version- A version number such as Docker version … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
docker --versionInstall once; it works for everything that needs Docker
Fill in 2 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
SIGNAL_SENDERE.164 number of the account registered in signal-cli (e.g. +15555550100)SIGNAL_DEFAULT_RECIPIENTE.164 number messaged by default; tools accept a per-call recipient override
Descriptions are as written by the maker.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --scope user signal --env SIGNAL_SENDER=your-value --env SIGNAL_DEFAULT_RECIPIENT=your-value -- docker run -i --rm -e SIGNAL_SENDER -e SIGNAL_DEFAULT_RECIPIENT ghcr.io/joshuawowk/signal-mcp:1.0.1 python3 /app/server.pyType /mcp in Claude Code
You should see Signal Messaging (via signal-cli) listed as connected
Try it
Use Signal Messaging (via signal-cli) and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Signal Messaging (via signal-cli) or shows a Signal Messaging (via signal-cli) tool in the answer, you are connected
6 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
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… · default http://host.docker.internal:8080/api/v1/rpcSIGNAL_TCP_HOSTsignal-cli daemon TCP host, used only for the receive-path health check · default 127.0.0.1SIGNAL_TCP_PORTsignal-cli daemon TCP port (daemon started with --tcp), used only for the receive-path health check · default 7583SIGNAL_INBOX_PATHPath of the replies inbox file inside the container (populated only by the subscriber process) · default /data/inbox.jsonlSIGNAL_POLL_INTERVALSubscriber poll cadence in seconds · default 3SIGNAL_INBOX_RETENTION_DAYSDays of replies kept in the inbox file · default 14
Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
2 setting(s) to fill in (SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT) · Install Docker on your computer first (one time)
Let AI install it
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Signal Messaging (via signal-cli) for Cursor on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "signal": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "SIGNAL_SENDER", "-e", "SIGNAL_DEFAULT_RECIPIENT", "ghcr.io/joshuawowk/signal-mcp:1.0.1", "python3", "/app/server.py" ], "env": { "SIGNAL_SENDER": "your-value", "SIGNAL_DEFAULT_RECIPIENT": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Signal Messaging (via signal-cli) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Docker (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
docker --version- A version number such as Docker version … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
docker --versionInstall once; it works for everything that needs Docker
Fill in 2 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
SIGNAL_SENDERE.164 number of the account registered in signal-cli (e.g. +15555550100)SIGNAL_DEFAULT_RECIPIENTE.164 number messaged by default; tools accept a per-call recipient override
Descriptions are as written by the maker.
Fill in your key
In the Signal Messaging (via signal-cli) settings, SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT is empty; add your key and save
Open the AI chat in Cursor in Agent mode
Try it
Use Signal Messaging (via signal-cli) and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Signal Messaging (via signal-cli) or shows a Signal Messaging (via signal-cli) tool in the answer, you are connected
6 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
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… · default http://host.docker.internal:8080/api/v1/rpcSIGNAL_TCP_HOSTsignal-cli daemon TCP host, used only for the receive-path health check · default 127.0.0.1SIGNAL_TCP_PORTsignal-cli daemon TCP port (daemon started with --tcp), used only for the receive-path health check · default 7583SIGNAL_INBOX_PATHPath of the replies inbox file inside the container (populated only by the subscriber process) · default /data/inbox.jsonlSIGNAL_POLL_INTERVALSubscriber poll cadence in seconds · default 3SIGNAL_INBOX_RETENTION_DAYSDays of replies kept in the inbox file · default 14
Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
2 setting(s) to fill in (SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT) · Install Docker on your computer first (one time)
Let AI install it
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Signal Messaging (via signal-cli) for VS Code on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "signal": { "type": "stdio", "command": "docker", "args": [ "run", "-i", "--rm", "-e", "SIGNAL_SENDER", "-e", "SIGNAL_DEFAULT_RECIPIENT", "ghcr.io/joshuawowk/signal-mcp:1.0.1", "python3", "/app/server.py" ], "env": { "SIGNAL_SENDER": "your-value", "SIGNAL_DEFAULT_RECIPIENT": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Signal Messaging (via signal-cli) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Docker (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
docker --version- A version number such as Docker version … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
docker --versionInstall once; it works for everything that needs Docker
Fill in 2 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
SIGNAL_SENDERE.164 number of the account registered in signal-cli (e.g. +15555550100)SIGNAL_DEFAULT_RECIPIENTE.164 number messaged by default; tools accept a per-call recipient override
Descriptions are as written by the maker.
Fill in your key
In the Signal Messaging (via signal-cli) settings, SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT is empty; add your key and save
Open the AI chat in VS Code in Agent mode
Try it
Use Signal Messaging (via signal-cli) and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Signal Messaging (via signal-cli) or shows a Signal Messaging (via signal-cli) tool in the answer, you are connected
6 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
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… · default http://host.docker.internal:8080/api/v1/rpcSIGNAL_TCP_HOSTsignal-cli daemon TCP host, used only for the receive-path health check · default 127.0.0.1SIGNAL_TCP_PORTsignal-cli daemon TCP port (daemon started with --tcp), used only for the receive-path health check · default 7583SIGNAL_INBOX_PATHPath of the replies inbox file inside the container (populated only by the subscriber process) · default /data/inbox.jsonlSIGNAL_POLL_INTERVALSubscriber poll cadence in seconds · default 3SIGNAL_INBOX_RETENTION_DAYSDays of replies kept in the inbox file · default 14
Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
For developers: Terminal commands and JSON settings
Installed on your computer
Claude Code
claude mcp add --scope user signal --env SIGNAL_SENDER=your-value --env SIGNAL_DEFAULT_RECIPIENT=your-value -- docker run -i --rm -e SIGNAL_SENDER -e SIGNAL_DEFAULT_RECIPIENT ghcr.io/joshuawowk/signal-mcp:1.0.1 python3 /app/server.pyClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"signal": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SIGNAL_SENDER",
"-e",
"SIGNAL_DEFAULT_RECIPIENT",
"ghcr.io/joshuawowk/signal-mcp:1.0.1",
"python3",
"/app/server.py"
],
"env": {
"SIGNAL_SENDER": "your-value",
"SIGNAL_DEFAULT_RECIPIENT": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"signal": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SIGNAL_SENDER",
"-e",
"SIGNAL_DEFAULT_RECIPIENT",
"ghcr.io/joshuawowk/signal-mcp:1.0.1",
"python3",
"/app/server.py"
],
"env": {
"SIGNAL_SENDER": "your-value",
"SIGNAL_DEFAULT_RECIPIENT": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"signal": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SIGNAL_SENDER",
"-e",
"SIGNAL_DEFAULT_RECIPIENT",
"ghcr.io/joshuawowk/signal-mcp:1.0.1",
"python3",
"/app/server.py"
],
"env": {
"SIGNAL_SENDER": "your-value",
"SIGNAL_DEFAULT_RECIPIENT": "your-value"
}
}
}
}Values you fill in
SIGNAL_SENDERrequired envE.164 number of the account registered in signal-cli (e.g. +15555550100)SIGNAL_DEFAULT_RECIPIENTrequired envE.164 number messaged by default; tools accept a per-call recipient overrideSIGNAL_RPC_URLenvsignal-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…SIGNAL_TCP_HOSTenvsignal-cli daemon TCP host, used only for the receive-path health checkSIGNAL_TCP_PORTenvsignal-cli daemon TCP port (daemon started with --tcp), used only for the receive-path health checkSIGNAL_INBOX_PATHenvPath of the replies inbox file inside the container (populated only by the subscriber process)SIGNAL_POLL_INTERVALenvSubscriber poll cadence in secondsSIGNAL_INBOX_RETENTION_DAYSenvDays of replies kept in the inbox file
Descriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account joshuawowk, which owns the repo
- ✓ Pass
Still maintained
Code last changed 30 days ago
- ✓ Pass
Has a licence
Uses MIT
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Published vulnerabilities (OSV.dev)
Not checked: only npm and PyPI packages with a version can be checked
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/joshuawowk-signal-mcp)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 0% of the other 6209 servers in this category
- Published to the registry more recently than 51% of the other 6209 servers in this category
- Basic checks equal to or better than 99% of the other 6209 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Signal Messaging (via signal-cli) safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed 30 days ago, and the latest version (1.0.1) reached the registry 30 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP
Cloudflare MCP servers
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Signal Messaging (via signal-cli) | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
signal-mcp
An unofficial MCP integration for Signal via signal-cli. It lets an MCP client send you Signal messages (task-done pings, blocking questions, permission requests) and read your replies.
Requirements: a running signal-cli JSON-RPC daemon (signal-cli daemon --http ..., plus --tcp ... if you want replies) and a Signal phone number already registered with signal-cli. This project does not register numbers, run the daemon, or talk to Signal's servers itself; it is only a client of your daemon. It is not affiliated with or endorsed by Signal Messenger or the Signal Foundation.
It consists of an MCP server (app/server.py) and an optional reply subscriber (app/subscriber.py) that fronts the existing signal-cli daemon without re-registering or bind-mounting its data directory.
Install
The image is published at ghcr.io/joshuawowk/signal-mcp and listed in the MCP Registry as io.github.joshuawowk/signal-mcp. Run with no arguments, the container starts the reply subscriber (the long-running mode used by the Compose deployment below); the MCP server is started explicitly.
MCP client over stdio (send-only)
docker run -i --rm \
--add-host host.docker.internal:host-gateway \ -e SIGNAL_SENDER=+15555550100 \ -e SIGNAL_DEFAULT_RECIPIENT=+15555550101 \ -e SIGNAL_RPC_URL=http://host.docker.internal:8080/api/v1/rpc \ ghcr.io/joshuawowk/signal-mcp:latest python3 /app/server.py --stdio
Notes:
- On Linux you can instead use
--network hostand drop the--add-hostandSIGNAL_RPC_URLsettings (the default127.0.0.1:8080then reaches your daemon). - With a bridge network the daemon must be reachable from the container. A daemon bound only to
127.0.0.1is not. The signal-cli HTTP endpoint is unauthenticated: do not expose it beyond a trusted interface. - A standalone stdio container has no subscriber, so replies are not collected:
signal_check_repliesreturns nothing andsignal_healthreports the receive path as down. For replies, use the Compose deployment below.
Compose deployment (send and receive replies)
See Setup.
Architecture
MCP client ──stdio──> docker exec ──> python3 /app/server.py ─┐
│ HTTP JSON-RPC host: signal-cli-daemon.service ◀── 127.0.0.1:8080 (synchronous)─┤ (send, version) ◀── 127.0.0.1:7583 (TCP stream)─┤ (receive notifications) │ docker container (signal-mcp, restart=unless-stopped) │ PID 1: subscriber.py ── persistent TCP socket ─────────────┘ └─> append /data/inbox.jsonl ◀── signal_check_replies reads
- No bind-mount of signal-cli data. The container is purely a client of the host daemon. Signal identity keys never enter the container.
- No re-registration. The Signal identity stays on the host.
- Two-channel daemon. Synchronous calls (send, version, health) go over HTTP on
:8080. Incoming-message notifications stream over a persistent TCP socket on:7583. The HTTP daemon'sreceivemethod is permanently locked by signal-cli's internal auto-receive loop, so TCP is the only path that works for replies. - One daemon flag added. The
--tcp 127.0.0.1:7583arg was added to the existingsignal-cli-daemon.serviceExecStart (see "Daemon configuration" below). HTTP behavior for any other consumer is unchanged.
Setup
git clone https://github.com/joshuawowk/signal-mcp && cd signal-mcp
cp .env.example .env # set SIGNAL_SENDER and SIGNAL_DEFAULT_RECIPIENT docker compose build docker compose up -d docker compose logs -f signal-mcp # watch the subscriber start up
Verify the daemon is reachable from the container:
docker exec signal-mcp python3 -c \
"import rpc; print(rpc.ping())"
expected: 0.14.3
Register the MCP server with Claude Desktop
Merge claude_desktop_config.snippet.json into ~/.config/Claude/claude_desktop_config.json under mcpServers:
"signal": {
"command": "sg", "args": ["docker", "-c", "exec docker exec -i signal-mcp python3 /app/server.py"] }
Restart Claude Desktop.
Why the sg wrapper
sg docker -c "…" runs the command under the docker supplementary group. This is required when the Claude Desktop process was started before your user was added to the docker group — existing sessions inherit a stale supplementary-group list and docker exec returns permission denied while trying to connect to the docker API at unix:///var/run/docker.sock, which surfaces in Claude Desktop's logs as write EPIPE / Server transport closed unexpectedly.
The exec inside the -c string replaces the temporary bash spawned by sg with the docker exec process, so SIGTERM/SIGPIPE from Claude Desktop reach the MCP server cleanly when the connection closes.
If you log out + back in (or reboot), all new processes inherit the docker group and the wrapper isn't strictly needed — but it's harmless to keep, and it makes the config portable across hosts where the group situation may vary. The signal server will appear in the MCP server list and its tools (signal_send_message, signal_send_question, signal_send_permission_request, signal_check_replies, signal_health) become available to any session.
Install the companion skill
An example agent skill lives in skill/SKILL.md (written for one person's setup; adapt the name and wording). Copy or symlink it into your agent's skills directory, for example:
mkdir -p <your-skills-dir>/signal
ln -sf "$PWD/skill/SKILL.md" /signal/SKILL.md
End-to-end test from a Claude session
Use signal_health to confirm the daemon is up, then signal_send_message
with text="signal-mcp end-to-end test from session XYZ" and session_id="signal-mcp-test-001". Then wait 30 seconds and call signal_check_replies with session_id="signal-mcp-test-001".
Reply with anything from your phone; the next signal_check_replies call should return your message.
Tools
| Tool | When to call |
|---|---|
signal_send_message(text, recipient?, session_id?) | Task-done pings, FYI updates. No reply expected. |
signal_send_question(question, options?, recipient?, session_id?) | Blocked, need an answer. options accepts a list ["A","B"], a JSON-array string '["A","B"]', or newline/comma-separated text — all normalized server-side. Response echoes options_parsed. |
signal_send_permission_request(action, context, recipient?, session_id?) | About to do something irreversible. Wait for explicit YES. |
signal_check_replies(since?, from_recipient?, session_id?, limit?) | Poll for replies. Filter by session_id. |
signal_health() | Full health: send path (daemon HTTP), receive path (TCP port + subscriber process liveness), and inbox status. ok is true only when send AND receive are healthy. An empty inbox is normal. Run first if anything fails. |
Reliability notes (Jun 2026)
- The inbox file (
/data/inbox.jsonl) is created at subscriber startup and is never deleted by retention pruning — an empty inbox stays as a 0-byte file. Previously, pruning removed the file entirely once all records aged out (14-day retention), which madesignal_check_replies/signal_healthlook like the subscriber was down.signal_check_repliesandsignal_healthalso ensure the file exists on every call. signal_healthandsignal_check_repliesreportsubscriber_running(scans/procforsubscriber.py) andreceive_channel_ok(TCP connect to the daemon's:7583), so a fresh session can distinguish "no replies yet" from "receive path broken".signal_send_questiontolerates clients that serialize theoptionslist into a string (see tools table).
Config (.env)
| Variable | Meaning |
|---|---|
SIGNAL_SENDER | E.164 of the registered signal-cli account. Required. |
SIGNAL_DEFAULT_RECIPIENT | E.164 to ping by default. Required. |
SIGNAL_RPC_URL | Daemon endpoint as seen from the container. Default http://127.0.0.1:8080/api/v1/rpc; with network_mode: host, that works. |
SIGNAL_TCP_HOST / SIGNAL_TCP_PORT | Daemon TCP stream for receive notifications. Defaults 127.0.0.1 / 7583. |
SIGNAL_POLL_INTERVAL | Subscriber poll cadence in seconds. |
SIGNAL_INBOX_RETENTION_DAYS | Days of replies kept in inbox.jsonl. |
SIGNAL_INBOX_PATH | Inbox file path inside the container. |
Operational
docker compose ps # status
docker compose logs -f signal-mcp # subscriber output docker exec signal-mcp tail -f /data/inbox.jsonl # raw replies docker compose restart signal-mcp # bounce the container docker compose down # stop
If the host daemon is restarted, the subscriber will reconnect on its next poll (errors back off up to 60 s).
Notes & limitations
- Linux host only.
network_mode: hostis a no-op on Docker Desktop for macOS/Windows. To move it: switch to a bridge network, setSIGNAL_RPC_URL=http://host.docker.internal:8080/api/v1/rpc, and addextra_hosts: ["host.docker.internal:host-gateway"]. - HTTP daemon polling. signal-cli's HTTP mode does not stream receive events; we poll. A TCP-mode daemon with WebSocket subscription would be lower-latency, but would require changing your existing daemon service.
- Attachments are skipped. The subscriber only persists text bodies. Reactions, typing indicators, and read receipts are ignored.
- The phone number is not memorized. It lives only in
.envand the registration snippet, both inside this project.
Daemon configuration
This project requires the host's signal-cli-daemon.service to expose both HTTP (for synchronous calls) and TCP (for streaming receive notifications). The unit file at ~/.config/systemd/user/signal-cli-daemon.service should have:
ExecStart=/usr/local/bin/signal-cli -a +15555550100 daemon --http 127.0.0.1:8080 --tcp 127.0.0.1:7583 --receive-mode on-start
To apply changes:
systemctl --user daemon-reload
systemctl --user restart signal-cli-daemon.service
A backup of the original unit file is written next to the live one with a .bak.YYYYMMDD-HHMMSS suffix the first time signal-mcp is set up.
Why not just use HTTP for receive?
signal-cli's HTTP daemon mode is synchronous-only. receive over HTTP always errors with "Receive command cannot be used if messages are already being received" because the daemon's internal receive loop owns the queue and HTTP has no way to deliver push events. TCP mode opens a persistent newline-delimited JSON-RPC stream and pushes receive notifications as they arrive — that's the path subscriber.py uses.