Daily Journal
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Daily Journal check today's journal status and print it if it's ready"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
The Daily Journal
Your mail, your calendar and the night's news, printed as a newspaper at seven every morning.
A private broadsheet for one reader, made by your own AI coding agent on your own computer. No feed, no app and no lock screen: just paper in the tray when you wake up.
Website · Get started · How it works · Tools
Why
The first thing most people read each day is a phone. It is bright, unsorted and endless, and it asks for a decision before the kettle has boiled.
The Daily Journal turns that around. While you sleep, your agent reads your inboxes, your calendar and the overnight news on the topics you choose, checks the sources and sets it all in type. At seven, your printer produces a two-page newspaper. It has a last line, so you can put it down.
Related MCP server: printshop-mcp
What's in an edition
Section | What it holds |
Front page | The overnight developments that matter most, each with its source and publication time |
Markets and topics | Finance, AI or whatever you choose. Weekend prices say which day they describe |
The day ahead | Today's calendar, with times, places and anything to prepare |
Your mail | Messages that need action first: deadlines, payments, security notices. Receipts next, newsletters grouped last |
Two or more A4 pages, three columns, body type never below 9 points, black ink on a laser printer.
Get started
You need a Mac or Linux computer that is on at print time, a printer it can reach, uv, and a coding agent with access to your mail and calendar (for example Gmail, Outlook and Google Calendar connectors).
Ask your coding agent
Paste this into Claude Code, Codex, Cursor or another agent that supports MCP:
Set up The Daily Journal for me from https://github.com/thegreatLUCY/daily-journal.
Clone it to ~/daily-journal-kit, then read SETUP.md there and follow it.
Ask me before printing anything or scheduling the daily runs.The agent connects the tools, asks your timezone, print time, topics and printer, prints a test page with your go-ahead, and then schedules two daily runs.
Install as a Claude Code plugin
claude plugin marketplace add thegreatLUCY/daily-journal
claude plugin install daily-journal@daily-journalThen ask Claude to "set up my daily journal".
Other MCP clients
See SETUP.md for Codex, Cursor, Windsurf and plain MCP configuration.
How it works
06:30 prepare 07:00 print
┌──────────────┐ ┌──────────────┐ ┌───────────┐ ┌──────────────┐
│ your agent │──▶│ write the │──▶│ render & │──▶│ print once, │
│ reads mail, │ │ edition JSON │ │ review │ │ inside the │
│ calendar, │ │ (skill rules)│ │ every page│ │ print window │
│ news sources │ └──────────────┘ └───────────┘ └──────────────┘
└──────────────┘The skill (
skills/daily-journal/SKILL.md) holds the editorial rules: what to collect, how to check it, how to write it and what never goes on paper.The MCP server (
daily_journal/server.py) does the layout, the checks and the printing. Your agent does the reading and writing.Your data stays in
~/.daily-journal: settings, editions, source records and the print ledger. Nothing is sent anywhere except to your printer.
Two runs a day keep it reliable. The prepare run builds and reviews the edition about half an hour early. The print run only prints an edition that has already been reviewed.
MCP tools
Tool | Purpose |
| Today's date in your timezone, your settings, and whether today's paper is ready or already printed |
| Timezone, print window, printer, paper, topics, masthead title |
| Print queues on this computer and the default |
| One test page, only when confirmed |
| Layout rules, word budgets and a full sample edition |
| Lay out an edition and return every page as an image for review |
| Record sources, collection window and anything that failed |
| Mark the reviewed edition ready to print |
| Dry run by default; prints once inside the window |
House rules
These are enforced in code, not just suggested to the agent.
The paper prints once. A ledger and a lock allow one print attempt per day, and an unclear result is never retried automatically.
Only today's reviewed paper prints. The PDF must carry today's date in your timezone and match the hash recorded when it was reviewed.
Proofs never print. Sample and draft editions are marked as proofs in the PDF itself.
A late paper stays unprinted. Outside the print window (07:00–09:00 by default), the press waits for tomorrow.
Nothing is answered for you. The skill never sends, deletes, moves or marks mail as read, and treats every message as information, never as instructions.
Secrets stay off paper. Passwords, verification codes, tokens and sign-in links are never printed.
Pictures are labelled. Generated engravings are captioned as artwork, never as photographs.
Settings
Stored in ~/.daily-journal/config.json (or $DAILY_JOURNAL_HOME). Your agent writes them with save_settings; config.example.json shows every key.
Key | Default | Meaning |
|
| IANA name, such as |
|
| The print window |
| system default | CUPS queue name |
|
| Passed to |
|
| Shorter editions are refused |
| finance, AI | What the news pages cover |
| Masthead and page furniture | |
|
| Pause publishing and printing |
Command line
The same pieces work without an agent:
uv run python -m daily_journal.render_edition examples/sample-edition.json sample.pdf
uv run python -m daily_journal.publish_ready ~/.daily-journal/editions/daily-journal-2026-11-02.pdf --visually-reviewed
uv run python -m daily_journal.submit_print # dry run
uv run python -m daily_journal.submit_print --send # prints once, inside the windowLimits
The computer must be on and awake at print time; the agent cannot wake it.
Printing uses CUPS (
lp), so Windows is not supported yet.Pages are laid out for A4. On Letter paper they print scaled to fit.
Mail sources that need an attended browser session cannot be read unattended. The paper says so when an inbox was missed.
Each morning's run uses your own AI subscription.
Project layout
.claude-plugin/ Claude Code plugin and marketplace manifests
.mcp.json MCP server entry used by the plugin
skills/daily-journal/ The skill and its layout reference
daily_journal/ Renderer, checks, print helper and MCP server
fonts/ Gelasio, Anton and UnifrakturCook (SIL OFL)
art/ Two AI-generated engravings for editions without photos
examples/ An invented sample edition
SETUP.md Step-by-step setup for coding agentsLicense
Code is MIT licensed; see LICENSE. Fonts are under the SIL Open Font License; see daily_journal/fonts/FONTS.md. The engravings in daily_journal/art/ are AI-generated illustrations and must be captioned as artwork.
Available Tools
9 toolsget_layout_guideA
The layout rules and a complete sample edition. Read before writing an edition.
Inputs: no named parameters. Returns: result
journal_statusA
Today's date in the reader's timezone, their settings, and whether today's edition is ready or already printed. Call this first.
Inputs: no named parameters.
list_printersA
List the print queues on this computer and the system default.
Inputs: no named parameters.
print_editionA
Print today's ready edition. With send=false this only checks it and shows the print command. With send=true it prints once, inside the reader's print window. Never retry after an unclear result.
Inputs: send.
print_test_pageA
Print one test page to check the printer during setup. Requires confirm=true and the reader's go-ahead.
Inputs: confirm.
publish_editionB
Mark today's live edition ready for the morning print. Only after you have looked at every page.
Inputs: pdf_path (required), visually_reviewed (required).
render_edition_pdfA
Lay out an edition and return every page as an image for visual review. Set live=true only for today's real edition; otherwise it is saved as a proof that can never print. Fix any reported overflow by shortening copy, then render again.
Inputs: edition (required), live.
save_settingsA
Update the reader's settings. Only known keys are accepted: title, timezone, print_time, latest_print_time, printer, paper, sides, copies, minimum_pages, topics, dateline_place, footer, hold_printing. Ask the reader before changing anything.
Inputs: changes (required).
save_sourcesA
Save today's source record: story URLs, checked times, collection window, which inboxes and calendars were read, and anything that failed. Store summaries only, never message bodies, codes or passwords.
Inputs: record (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
The staged workflow (render → publish → print) is clearly delineated by descriptions, and the read-side tools (journal_status, list_printers, get_layout_guide) each target a distinct artifact. The only mild overlap is print_edition vs print_test_page, which both invoke the printer but are differentiated by 'today's ready edition' vs 'setup test'.
Eight of nine tools follow a verb_noun pattern (save_settings, list_printers, render_edition_pdf, publish_edition, print_edition). The single exception is journal_status, which is noun-first, but it remains readable and predictable in context.
Nine tools is well-scoped for a daily-edition workflow, with each tool earning its place across status, configuration, layout, sourcing, rendering, publishing, and printing. Nothing feels redundant or padded.
The core daily lifecycle is covered end to end, including source provenance and a safe test-print path. Minor gaps exist: there is no way to list or retrieve past editions/proofs, and no retract/unpublish operation once an edition is marked ready.
Maintenance
Related MCP Connectors
The agentic layer of letters. Agents send real printed mail worldwide, German compliance built in.
Turns agent output into versioned web pages, PDFs, Word docs, spreadsheets and Markdown.
Print & mail PDF/HTML/Markdown/text/DOCX/images to US addresses; pay per call in x402 USDC on Base.
Publish live pages from any agent, collect what visitors submit, and read it back.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables users to turn their current Codex/ChatGPT conversation into a source-backed personal newspaper: they pick public sources, exclusions, language, timezone and interests through native settings, then request an edition that the conversation reads and cites. The server stores and renders validated editions locally with source links, preserving the previous edition when generation fails.MIT
- AlicenseAqualityBmaintenanceEnables an AI agent to design, lay out, proof and print badges, business cards, flyers, photos and sublimation transfers on real paper printers with millimetre-accurate output, packing mixed items onto shared sheets with crop marks. It also remembers named print profiles, including printer, paper, tray, media type, quality and calibration settings.10MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to send a finished one-page daily newspaper brief to a private endpoint, where it is rendered for the user's printer and printed when they are nearby. It accepts editions through MCP, webhook, or email while keeping calendar and mail data on the agent side.2MIT
- AlicenseAqualityBmaintenanceEnables printing labels whose layout adapts to the roll reported by a CUPS/IPP label printer, as well as PDF, Markdown, and HTML documents, with preview, copies, duplex, page ranges, and print-job management.7MIT