signal-cli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NTFY_TOPIC | No | Optional: ntfy topic for push notifications. If set, enables notifications on new proposals. | |
| NTFY_BASE_URL | No | Optional: ntfy server base URL. Defaults to https://ntfy.sh. | https://ntfy.sh |
| GUI_PUBLIC_URL | No | Optional: public URL for the approval GUI, used for actionable push notifications (e.g., https://signal-mcp.tailnet.ts.net/). | |
| SIGNAL_ACCOUNT | Yes | Your phone number in E.164 format (e.g., +1234567890) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| proposeSignalMessageA | Proposes sending a Signal message to an individual. AWAITS human approval in a local GUI — the call may take several minutes. This is not an error; wait patiently. Nothing is sent without approval. |
| proposeSignalGroupMessageA | Proposes sending a Signal message to a group. AWAITS human approval in a local GUI — the call may take several minutes. This is not an error; wait patiently. Nothing is sent without approval. |
| proposeSignalGroupCreationA | Proposes creating a new Signal group. AWAITS human approval in a local GUI — the call may take several minutes. This is not an error; wait patiently. Nothing is sent without approval. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: sending to an individual, sending to a group, and creating a group. The recipient type and action are explicit in the names, leaving no ambiguity.
All tools follow a consistent 'propose[Action]' pattern with clear noun phrases (SignalMessage, SignalGroupMessage, SignalGroupCreation). The naming is uniform and predictable.
At 3 tools, the count is at the low end of the typical range. While each tool earns its place, the server feels minimal and could benefit from a few more operations to feel well-rounded.
The server covers sending messages and creating groups but lacks any receive, list, or management capabilities. For a Signal client, this is a significant gap that would prevent agents from performing common workflows.