MCP server for Dayflow screen time tracker. Connects Claude Code (or any MCP client) to your local Dayflow data for querying timeline activities, observations, journal entries, and daily stats. Read-only access - your data never leaves your machine.
- Query timeline activities by day, date range, or keyword search
- Get raw screen observations (granular transcriptions)
- Read journal entries with intentions, reflections, and AI summaries
- Category breakdown and time statistics per day
- Access daily standup entries
- Browse tracked days and recent activity
| Tool | Description |
|---|---|
dayflow_get_timeline |
Timeline cards for a specific day |
dayflow_get_timeline_range |
Timeline cards across a date range |
dayflow_get_observations |
Raw granular screen observations for a day |
dayflow_get_journal |
Journal entry (intentions, reflections, summary) |
dayflow_list_journal_days |
List days with journal entries |
dayflow_get_categories |
Activity categories with colors and descriptions |
dayflow_get_daily_stats |
Category breakdown and time stats for a day |
dayflow_search_timeline |
Search activities by keyword |
dayflow_get_recent_activity |
Most recent timeline activities |
dayflow_get_standup |
Daily standup entry |
dayflow_list_tracked_days |
List days with tracked data |
bun installclaude mcp add dayflow --transport stdio --scope user \
-- bun /path/to/dayflow-mcp/server.tsIn Claude Code, run /mcp and check that dayflow shows as connected.
The server reads directly from Dayflow's local SQLite database at ~/Library/Application Support/Dayflow/chunks.sqlite. It opens the database in read-only mode, so it cannot modify your data.
Categories are read from macOS UserDefaults (teleportlabs.com.Dayflow domain) with a fallback to distinct values from the database.
Dayflow uses 4 AM day boundaries - a "day" runs from 4 AM on the calendar date to 4 AM the next day.

