aboutsummaryrefslogtreecommitdiff
path: root/mcp/README.org
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-12 15:26:22 -0500
committerCraig Jennings <c@cjennings.net>2026-06-12 15:26:22 -0500
commit13256aad033f84c0854f2d562685ea808a5ec619 (patch)
treebe030ced846ce87eabd9f8c18dac5e221b0611d3 /mcp/README.org
parent21ab10ef9e2fff9b4726695036e95e33937e1fa9 (diff)
downloadrulesets-13256aad033f84c0854f2d562685ea808a5ec619.tar.gz
rulesets-13256aad033f84c0854f2d562685ea808a5ec619.zip
chore: delete the page-signal pager wrapper
Remove the page-signal CLI wrapper, its workflow, and the references in INDEX.org, broadcast.org, and mcp/README.org. The signal MCP server stays. It's the two-way path and a separate capability. The pager number had deregistered and the send-only wrapper isn't worth re-registering.
Diffstat (limited to 'mcp/README.org')
-rw-r--r--mcp/README.org2
1 files changed, 1 insertions, 1 deletions
diff --git a/mcp/README.org b/mcp/README.org
index 30dc082..ac65ffd 100644
--- a/mcp/README.org
+++ b/mcp/README.org
@@ -90,4 +90,4 @@ Prerequisites on a fresh machine, in order:
2. Register the dedicated pager account. Signal requires a captcha for registration: run =signal-cli -a +<number> register=, follow the printed =signalcaptchas.org= link, solve it, and pass the resulting token to =signal-cli -a +<number> register --captcha <token>= within a minute or two before it expires. Signal then texts a code to the number; verify with =signal-cli -a +<number> verify <code>=.
3. =make install-mcp= registers =signal-mcp= pointed at that =--user-id=.
-The =--user-id= is a *dedicated* number (a Google Voice number registered to =signal-cli=), not Craig's primary. Signal mobile won't push-notify a message an account sends to itself, so paging from the primary to itself is silent; a distinct sender account reaching Craig's account notifies normally. Craig's account hides its phone number under phone-number privacy, so the destination is its stable account UUID rather than a number. The same account and recipient back the =page-signal= CLI wrapper (=PAGE_SIGNAL_ACCOUNT= / =PAGE_SIGNAL_TO=). The MCP server is the two-way path (=receive_message= to listen for replies); =page-signal= is the fast send-only path.
+The =--user-id= is a *dedicated* number (a Google Voice number registered to =signal-cli=), not Craig's primary. Signal mobile won't push-notify a message an account sends to itself, so paging from the primary to itself is silent; a distinct sender account reaching Craig's account notifies normally. Craig's account hides its phone number under phone-number privacy, so the destination is its stable account UUID rather than a number. The MCP server is the two-way path (=receive_message= to listen for replies).