mirror of
https://github.com/kuhyx/screen-locker.git
synced 2026-11-10 21:27:13 +01:00
Krzysztof kuhy Rudnicki
494cc74bb5
Expose the screen-locker's compliance and lock-decision state as read-only MCP tools (screen_locker._mcp) so Claude Code and its subagents can query workout status without shelling out to the CLI or opening the Tk window. - _mcp.py: FastMCP stdio server. Read-only tools get_status, get_summary, explain_lock, get_flags. Import leaf over stdout-free status functions (gather_status, format_summary_line, explain_lock_decision, predicates); logs to stderr. NO write/action tools by design — workouts are logged only from RunnerUp-verified TCX data, never from a caller's claim. No tool exposes the sync token or any HMAC key. - .mcp.json + scripts/setup_mcp.sh: registration via a dedicated ~/.venvs/screen-locker-mcp interpreter; mcp is an optional-dep. - 100% coverage of the new module; verified end-to-end over stdio. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LQGQj8Ne6TriBExv91nG8v
33 lines
1.5 KiB
Markdown
33 lines
1.5 KiB
Markdown
# screen-locker
|
|
|
|
Tkinter/systemd screen locker with workout tracking, sick-day management, and
|
|
wake-alarm integration. It enforces a workout cadence by locking the screen
|
|
until a RunnerUp-verified (or explicitly justified) workout is logged.
|
|
|
|
## MCP server (Claude Code integration)
|
|
|
|
screen-locker exposes a **read-only** MCP server (`screen_locker._mcp`) so
|
|
Claude Code and its subagents can query workout compliance and the
|
|
lock-decision state through typed tools — without shelling out to the
|
|
`screen-locker-status` CLI or opening the Tk window.
|
|
|
|
- **Read-only tools:** `get_status` (full status snapshot), `get_summary`
|
|
(one-line i3blocks summary + `ok`/`warn`/`lock` state word), `explain_lock`
|
|
(why the screen is / isn't locked right now), `get_flags` (the individual
|
|
boolean lock-decision predicates for today).
|
|
- There are **no write/action tools**, by design. Nothing here logs a workout
|
|
or mutates state — workouts are logged only from RunnerUp-verified TCX data,
|
|
never from a caller's claim. No tool exposes the sync token or any HMAC key.
|
|
|
|
The `mcp` SDK is an optional dependency (`pip install -e '.[mcp]'`), kept out of
|
|
the CLI/systemd system-python path. One-time setup of the dedicated venv that
|
|
Claude Code spawns:
|
|
|
|
```bash
|
|
./scripts/setup_mcp.sh
|
|
```
|
|
|
|
Registration lives in the checked-in [`.mcp.json`](./.mcp.json) (project scope).
|
|
Restart Claude Code in this repo and approve the project MCP-server prompt for it
|
|
to load. Verify with `claude mcp list`.
|