Signal Messaging (via signal-cli) MCP Server
Send Signal messages and read replies through your own signal-cli JSON-RPC daemon (unofficial).
Signal Messaging (via signal-cli) scores 37 (Limited), licensed MIT and written in Python. It installs as a local process. It does not declare tools yet. Filed under Developer tools. GitHub shows 0 stars. Install configs are generated for 10 clients. Being listed in the registry is not the same as being vendor-official.
Limited trust
37 of 100 from six public signals. Nobody can buy a point.
- OSI-style license: mit.
License, quality and maintenance
Where the 37 comes from
0 + 20 + 0 + 10 + 4 + 3 = 37. Each factor is capped, so no single signal can carry a listing.
Active in the official MCP registry, plus a known vendor namespace.
Registry: 0 of 30 points.How recently the repository saw a commit or release.
Maintenance: 20 of 20 points.GitHub stars and weekly downloads, on a log scale.
Popularity: 0 of 20 points.A clear, OSI-style open-source license.
License: 10 of 10 points.Not archived, a secure install path, a pinned version.
Security: 4 of 10 points.A real summary, a README with depth, listed tools.
Docs: 3 of 10 points.Install
Pick your client, copy the config, paste it in.
Needs Cursor or VS Code installed on this device. The button opens the app and asks you to confirm before it adds the server.
{ "mcpServers": { "joshuawowk-signal-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/joshuawowk/signal-mcp:1.0.1" ], "env": { "SIGNAL_SENDER": "", "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
| Name | Required | Notes |
|---|---|---|
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 | Optional | 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 | Optional | signal-cli daemon TCP host, used only for the receive-path health check |
SIGNAL_TCP_PORT | Optional | signal-cli daemon TCP port (daemon started with --tcp), used only for the receive-path health check |
SIGNAL_INBOX_PATH | Optional | Path of the replies inbox file inside the container (populated only by the subscriber process) |
SIGNAL_POLL_INTERVAL | Optional | Subscriber poll cadence in seconds |
SIGNAL_INBOX_RETENTION_DAYS | Optional | Days of replies kept in the inbox file |
Tools
All capabilitiesTools show up when the registry metadata or the repository README lists them. Public READMEs are read directly. A GitHub token is used only when one is already configured.
About
Send Signal messages and read replies through your own signal-cli JSON-RPC daemon (unofficial).
Frequently asked questions
What is Signal Messaging (via signal-cli) MCP Server?
Send Signal messages and read replies through your own signal-cli JSON-RPC daemon (unofficial).
How do I install Signal Messaging (via signal-cli) MCP Server in Claude Desktop, Cursor, or VS Code?
Pick your client in the Install section on this page and copy the generated config into the client's config file. Step-by-step guides: Claude Desktop, Cursor, and VS Code. Signal Messaging (via signal-cli) MCP Server runs locally from the Docker image ghcr.io/joshuawowk/signal-mcp:1.0.1 with the command docker run -i --rm ghcr.io/joshuawowk/signal-mcp:1.0.1.
Is Signal Messaging (via signal-cli) MCP Server free and open source?
Yes. Signal Messaging (via signal-cli) MCP Server is released under the MIT license, an OSI-approved open-source license, so you can use, modify, and self-host it under those terms.
Does Signal Messaging (via signal-cli) MCP Server support remote (HTTP) connections?
No remote endpoint is listed for Signal Messaging (via signal-cli) MCP Server. It runs locally on your machine over stdio, started by your MCP client.
How is Signal Messaging (via signal-cli) MCP Server's trust score calculated?
Signal Messaging (via signal-cli) MCP Server scores 37 out of 100 (Limited). The score adds six capped public signals: registry status, maintenance, popularity, license, documentation, and security. Nobody can pay for points. Read the methodology for the full formula.
Reviews
No reviews yet—Be the first to review
No published reviews yet. Used it? Tell the next person how it went.
Sign inA verified email is required to review this server.
Add badge to your README
Paste either snippet into the repository README. The image links to this listing.
