Building a Daily Chinese Diary Habit with Notion MCP + Claude

enoki — Sun, 29 Mar 2026 12:56:09 +0000

This is a submission for the Notion MCP Challenge

What I Built

I built an automated workflow for my daily Chinese learning habit called "中国語3行日記" (3-Line Chinese Diary). Every day, I write a 3-sentence Chinese diary entry based on a daily theme, get it corrected by Claude, and post it to Bluesky — all without leaving Claude's chat UI.

The system is powered by Notion + Claude MCP + GitHub Actions:

Notion stores the daily themes (Questions DB) and my answers with correction notes (Answers DB)
Claude MCP fetches the day's theme, corrects my Chinese, records the answer and notes back to Notion, and helps me analyze my writing patterns over time
GitHub Actions runs a daily cron job at 21:00 JST to automatically post scheduled answers to Bluesky

As of today, I've kept this habit going for over 225 days.

Video Demo

Show us the code

github.com/enoki-85/3-line-diary-scheduler

How I Used Notion MCP

The Daily Workflow

Each session follows this flow entirely within Claude's chat UI:

I tell Claude which day's theme to fetch → Claude retrieves it from the Notion Questions DB via MCP
I write my 3-sentence Chinese diary entry
Claude corrects my Chinese and explains the mistakes
Claude registers the final answer, pinyin, and correction notes to the Notion Answers DB via MCP
GitHub Actions picks it up at 21:00 JST and posts it to Bluesky automatically

Looking Back at My Writing Patterns

Beyond the daily workflow, I can ask Claude to retrieve past answers from Notion and review my correction notes. Since all notes are stored in Notion, I can look back at specific entries and spot recurring mistakes. I'm also planning to build a GitHub Actions workflow that summarizes each month's entries into a dedicated Notion page, which would make longer-term pattern analysis much easier.

Why This Stack Works

Before this system, I went through a few iterations. I started by handwriting entries, then manually formatting and posting them. I later built a web app to streamline the process — but it required server costs, and since the themes are sourced from copyrighted material, I couldn't make the repo public. I was also using the Claude API separately, adding unnecessary cost on top of my Claude MAX plan.

Switching to Notion MCP + Claude solved all of this:

No extra server costs — GitHub Actions handles the automation for free
No API costs — everything runs within my Claude MAX plan
No friction — theme retrieval, correction, and Notion registration all happen in one chat
The repo is private-safe — theme data lives in Notion, not in the codebase

The most important shift was removing everything except the actual learning. Writing and getting corrected is the core habit. Everything else — fetching themes, formatting posts, storing notes, posting to Bluesky — is now invisible. On days when motivation is low, having a smaller, frictionless target makes all the difference. Over 225 days in — though the Notion MCP setup is only about a month old — I feel like I can keep this going for a long time to come.

Forem: enoki