Separate controls from calculations
If the GUI, CLI, and MCP each held their own state, the same input could produce different results or saved settings. Clocks, timers, and settings are managed by one Core, with each interface calling the same calculations and persistence operations.
Version 0.2.8 separated settings and rendering into modules. The cleanup in 0.2.19 removed old API aliases and legacy skin loading from the current interfaces. A shared catalogue provides the same design choices to the GUI and external controls.
Check Help for the running version
The Store version's command alias is ntpclockmonitorctl. After an update, check Help in the running version for available commands.
ntpclockmonitorctl helpExternal controls can set explicit date-and-time targets and scheduled starts that do not have input fields in the GUI. Start the clock app before connecting through MCP. The app does not register itself automatically with an MCP client.
Local communication on the same PC
The local API uses authenticated TCP JSON communication, with credentials generated for each launch and connections limited to the same PC. This product website does not connect to or control the clock app.