daylens-mcp
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., "@daylens-mcp show me my focus score for yesterday"
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.
daylens-mcp
An MCP server that lets Cursor and Claude answer "what was I working on?" from your local Daylens timeline — no cloud, no API keys.
The problem
You ask your AI assistant what you did this morning. It guesses.
It doesn't know you spent three hours in Cursor on the auth refactor, or that you context-switched 200 times before lunch. It wasn't there. Daylens was — it logged every session, labeled every work block, scored your focus — but your AI tools can't see any of it.
You shouldn't have to reconstruct your own day from memory just to fill a timesheet or pick up where you left off.
Related MCP server: AI Memory MCP
What it does
Ask in plain language. Get answers grounded in your actual machine:
You › what was I working on this morning?
• 06:40–09:30 (2h 50m) — Tax Filing, Email & Planning
• 09:30–12:57 (3h 26m) — Mixed Development & Research
Top app: Codex | 219 context switches
• 12:57–13:12 (15m) — X.com, YouTube, EmailWorks in Claude Code, Cursor, Claude Desktop, and Windsurf.
Install
Requires Daylens on macOS and Node.js 22+.
Claude Code — one command:
claude mcp add daylens -- npx -y daylens-mcpCursor — add to ~/.cursor/mcp.json:
{
"mcpServers": {
"daylens": {
"command": "npx",
"args": ["-y", "daylens-mcp"]
}
}
}All clients — auto-detects Claude Code, Cursor, Desktop, and Windsurf:
git clone https://github.com/irachrist1/daylens-mcp.git && cd daylens-mcp && bash install.shRestart your client after install.
How it works
Read-only bridge. Opens your Daylens SQLite database in read-only mode. Nothing is written, nothing leaves your Mac.
Labeled blocks, not raw logs. Queries AI-labeled work sessions like "Mixed Development & Research" — not "Chrome: 6 hours".
Five tools, natural questions. Timeline, focus stats, app usage, keyword search, and recent activity. Your assistant picks the tool; you just ask.
On demand, no daemon. Starts when your AI client needs it, exits when the session closes. No background process, no network calls.
Pre-computed summaries. Pulls focus scores, streaks, and daily summaries Daylens already computed — fast answers without re-analyzing raw sessions.
MIT License · Built by Christian Tonny
Available Tools
5 toolsget_app_usageA
Get a breakdown of which apps you used and for how long. Defaults to today.
Inputs: date.
get_focus_statsB
Get focus score, active time, and productivity metrics from Daylens. Defaults to today.
Inputs: date.
get_recent_activityB
See what you've been doing in the last N minutes according to Daylens.
Inputs: minutes.
get_timelineA
Get your Daylens work timeline for a day — labeled work blocks with durations and context. Defaults to today.
Inputs: date.
search_workA
Search Daylens work history by app name, label, category, or description.
Inputs: query (required), days.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a distinct purpose: timeline for daily blocks, focus stats for metrics, app usage for breakdown, search for querying history, and recent activity for up-to-the-minute info. No two tools clearly overlap.
Four tools consistently use the get_ prefix (get_timeline, get_focus_stats, get_app_usage, get_recent_activity), but search_work breaks the pattern. While still readable, the inconsistency is mildly noticeable.
Five tools is well-scoped for a personal analytics server, covering the main ways to access Daylens data without being bloated or sparse.
The set covers all the typical read-only needs for a work-tracking service: daily overview, metrics, detailed usage, search, and real-time activity. No obvious gaps for this domain.
Maintenance
Related MCP Connectors
Mac & Windows: let ChatGPT, Claude & Cursor use your email, calendar, iMessage, Teams, files.
Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session.
Project memory for every AI. Pick up where you left off in Claude, ChatGPT or Cursor, with a team.
One memory for Claude, ChatGPT and Cursor, kept on your computer. Optional sync, encrypted first.
Related MCP Servers
- AlicenseAqualityCmaintenanceGives Claude persistent, local context about how you work, your weekly agenda, and shipped work, with automatic work logging and git integration—all stored privately on your machine.12MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to semantically search your entire local conversation history from Claude Desktop, ChatGPT and Claude Code, and to retrieve, browse, ingest and report on those conversations. All embeddings run locally, so no cloud, API keys, or data leave your machine.2MIT
- AlicenseNot gradedqualityBmaintenanceProvides a local AI assistant with tools to query your computer's episodic memory, such as where you were, what you were working on, activity summaries, and timeline details, all sourced from a privacy-filtered SQLite database.MIT
- FlicenseNot gradedqualityBmaintenanceLets Claude answer questions about your own past computer activity by reading a local, AES-256-encrypted database of screenshots, OCR text, calendar events, conversations, and location traces in read-only mode. Queries like "What was I doing last Wednesday at noon?" are resolved entirely on your machine, with no network service or cloud involvement.-