daylens-mcp
Connects AI assistants like Cursor and Claude to your local Daylens timeline so they can answer questions about your past work sessions, no cloud or API keys needed.
README
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.
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, Email
Works 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-mcp
Cursor — 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.sh
Restart 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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.