Signal MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIGNAL_CONFIG | Yes | Path to the signal.config.json configuration file |
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 |
|---|---|
| list_checksD | Unavailable: signal-mcp is not configured for this project. Call it to see why. |
| start_checkB | Unavailable: signal-mcp is not configured for this project. Call it to see why. |
| start_checksB | Unavailable: signal-mcp is not configured for this project. Call it to see why. |
| run_checkA | Unavailable: signal-mcp is not configured for this project. Call it to see why. |
| run_checksB | Unavailable: signal-mcp is not configured for this project. Call it to see why. |
| get_run_statusB | Unavailable: signal-mcp is not configured for this project. Call it to see why. |
| list_runsC | Unavailable: signal-mcp is not configured for this project. Call it to see why. |
| get_run_summaryC | Unavailable: signal-mcp is not configured for this project. Call it to see why. |
| diff_runsB | Unavailable: signal-mcp is not configured for this project. Call it to see why. |
| get_log_sliceC | Unavailable: signal-mcp is not configured for this project. Call it to see why. |
| rerun_failedC | Unavailable: signal-mcp is not configured for this project. Call it to see why. |
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 11 tools
All tool descriptions are identical unavailable messages, so disambiguation relies solely on names. start_check/start_checks and run_check/run_checks are ambiguous in scope, and start vs. run overlap heavily, making it difficult for an agent to choose the correct intent.
Tool names consistently use lowercase snake_case with a verb_noun pattern (list_checks, get_run_status, diff_runs). Minor inconsistencies exist between singular/plural variants (start_check vs. start_checks) and synonymous verbs (start/run), but the overall pattern is predictable.
11 tools is within the ideal 3-15 range for a check/run management server. Each name suggests a distinct operational purpose, and the count feels appropriately scoped without redundancy or bloat.
The tool surface covers the core lifecycle of checks and runs: listing, starting, running, status, summaries, diffs, logs, and reruns. The only notable gap is the absence of a cancel/stop or delete operation, which is a minor missing action for a management toolset.