Signal MCP
An MCP integration for signal-cli that allows AI agents to send and receive Signal messages.
Features
- Send messages to Signal users
- Send messages to Signal groups
- Receive and parse incoming messages
- Async support with timeout handling
- Detailed logging
Prerequisites
This project requires signal-cli to be installed and configured on your system.
Installing signal-cli
-
Install signal-cli: Follow the official installation instructions
-
Register your Signal account:
signal-cli -u YOUR_PHONE_NUMBER register
-
Verify your account with the code received via SMS:
signal-cli -u YOUR_PHONE_NUMBER verify CODE_RECEIVED
For more detailed setup instructions, see the signal-cli documentation.
Installation
pip install -e .
# or use uv for faster installation
uv pip install -e .
Usage
Run the MCP server:
./main.py --user-id YOUR_PHONE_NUMBER [--transport {sse|stdio}]
API
Tools Available
send_message_to_user: Send a direct message to a Signal usersend_message_to_group: Send a message to a Signal groupreceive_message: Wait for and receive messages with timeout support
Development
This project uses:
- MCP for agent-API integration
- Modern Python async patterns
- Type annotations throughout
Metadata
Release files for iflow-mcp_rymurr-signal-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_rymurr_signal_mcp-0.1.1.tar.gz | 18.3 kB | Without provenance | Details for iflow_mcp_rymurr_signal_mcp-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_rymurr_signal_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_rymurr_signal_mcp-0.1.1-py3-none-any.whl |
Total release size: 23.8 kB
Release files / iflow_mcp_rymurr_signal_mcp-0.1.1.tar.gz
| Download URL | iflow_mcp_rymurr_signal_mcp-0.1.1.tar.gz |
|---|---|
| Size | 18.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
57c628965fa423d813484bb8ebce318dedaaaae03250638b0b600de1007672a3
|
|
BLAKE2b-256 checksum How to use checksums |
8f844267f340efc5512ab4fd39ab4fe65b02b2f69a1f2f760ac1eec5f76ed3cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.0 {"installer":{"name":"uv","version":"0.10.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_rymurr_signal_mcp-0.1.1-py3-none-any.whl
| Download URL | iflow_mcp_rymurr_signal_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
243ef2b41f5145f9341d20cbf606b25e3a011db8bff6a297f91a6a49d44fe2ad
|
|
BLAKE2b-256 checksum How to use checksums |
ab6be94022868726906a636563bdd8128eefeb6efe635629c7968307d40d3d5d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.0 {"installer":{"name":"uv","version":"0.10.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for iflow-mcp_rymurr-signal-mcp 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.