Summary
The conversation becomes the journal entry.
Rather than journaling and then talking about it, the session is the entry: timestamped as it happens, summarised when it closes, and left on disk as Markdown you can read without this server.
What it is
A journaling MCP server that saves interactive sessions as Markdown files. Each exchange is recorded with its timestamp, and closing a session writes a dated header, the transcript, an emotional analysis and the recurring themes into a file in your journal directory.
What you get
- A journaling session started and closed on demand
- Each exchange recorded with its timestamp
- A session summary written into the entry, with emotional analysis and recurring themes
- The five most recent entries read back
- Entries stored as dated Markdown files, also reachable at journals://recent
Requirements
Python with uv, pointed at a local checkout. Entries are written to a journal directory, which defaults to ~/Documents/journal and can be pointed elsewhere; the filename prefix and file extension are configurable. No account, no key.