State and logs

Logs and events

logs.ts keeps the last 2000 entries in memory for the Logs page and the admin tools: MCP calls, actions from the UI, servers’ standard error and the hub’s own notes. Calls and actions are also saved to activity.json a few seconds after they happen and on shutdown, so history survives a restart; server output stays in memory.

Everything also goes to the process output: structured events as JSON lines on stdout for log collectors, plain lines on stderr. Long-term retention is the collector’s job.

Data directory

• Directory$MCPYARD_DATA_DIR/

  • keys.json keys, with token hashes only
  • settings.json settings saved from the UI
  • state.json servers switched off from the UI
  • versions.json recorded and previous versions of hub-owned packages
  • activity.json saved MCP calls and UI actions
  • session.key signs the UI cookies
  • Directorypackages/

    • Directory<server>/

      • Directory<version>/ an installed package

        • …
  • Directorycache/ npm and uv caches

    • …
  • Directorypython/ uv-managed Python

    • …

Files are written to a temporary name, then renamed, so a crash never leaves half a file. The server file is the exception, written in place as Configuration explains.