From cfaff12c2425c0e28953981e5b06b54fd60e25cf Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Tue, 2 Jun 2026 18:03:28 -0500 Subject: feat(page-signal): route pages through a dedicated Signal pager account Paging never actually reached the phone before. signal-cli was registered as my primary number, so a page was that account messaging itself, and Signal mobile doesn't push-notify a self-message. I registered signal-cli with a separate Google Voice number (profile "Claude Pager") and pointed everything at it. page-signal now sends from that account to my Signal account by default, so a page lands as a normal third-party message and rings the phone. The old --note-to-self default is gone, since note-to-self on the pager account wouldn't reach me. Sender and default recipient now come from PAGE_SIGNAL_ACCOUNT and PAGE_SIGNAL_TO with baked-in defaults. The send command pins the sender with -a, and --to also accepts a Signal account UUID, since my account hides its phone number. servers.json points signal-mcp at the new number. Verified end-to-end: live sends from the pager account notified the phone, and signal-mcp shows connected. --- mcp/servers.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'mcp/servers.json') diff --git a/mcp/servers.json b/mcp/servers.json index 5554c04..98e36ba 100644 --- a/mcp/servers.json +++ b/mcp/servers.json @@ -65,7 +65,7 @@ "command": "/home/cjennings/.local/share/signal-mcp/.venv/bin/python", "args": [ "/home/cjennings/.local/share/signal-mcp/signal_mcp/main.py", - "--user-id", "+15103169357", + "--user-id", "+15045173983", "--transport", "stdio" ], "env": {} -- cgit v1.2.3