get_pomodoro_stats
Get pomodoro session statistics for the last N days
LABSCO SUMMARY
It reads the files the app already wrote, and never writes back.
Because it goes at the on-disk database rather than a cloud API, there is nothing to authorise and no sync to wait for — but you see the last state Chrome or the app flushed to disk, not necessarily this second's. The server opens those files read-only and caches for 30 seconds; it cannot modify your data.
What it is
A read-only reader for Focus To-Do's local storage. It finds and parses the app's IndexedDB — Chrome's LevelDB format, used by both the Windows Store app and the browser extension — decodes the records, and serves your tasks and sessions as tools. Nothing goes to a server.
What you get
- Projects listed, with the app's own system projects hidden by default —
list_projects - Tasks filtered by project and by status:
active,completedorall—list_tasks - Tasks found by name —
search_tasks - One task in full, subtasks included —
get_task,list_subtasks - Pomodoro statistics broken down by day over the last N days —
get_pomodoro_stats - Auto-detection of the database across Chrome, Chromium, Brave, Edge and Vivaldi profiles including Flatpak and Snap, plus the Windows Store app; override it with
FOCUS_TODO_IDB_PATH
Requirements
Focus To-Do installed on the same machine, either as the Chrome extension or the Microsoft Store app, on Linux, macOS or Windows. Node.js 18+. No account login, no API key, no export step. Registered with claude mcp add --scope user focus-todo node "<YOUR_PATH_TO_FOCUS_TODO_MCP>/index.mjs".
Setup effort
Build from source — git clone https://github.com/b0r1sOm4g0/focus-todo-mcp
USE CASES
01
Reviewing where your focused hours actually went
Pull Pomodoro statistics by day over the last stretch and compare them against the tasks that were open, instead of eyeballing the app's charts.
02
Planning tomorrow from what is still open
List the active tasks in a project and open the ones that matter to see their subtasks, then decide the order in the conversation.
03
Finding a task you half remember
Search by name across projects rather than clicking through the app, then read it in full with its subtasks.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_task
Get full details of a task including its subtasks
list_projects
List all Focus To-Do projects
list_subtasks
List subtasks for a specific task
list_tasks
List tasks, optionally filtered by project or status
search_tasks
Search tasks by name
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected. There is no tool to add, complete or edit a task; the server opens your database read-only.
Requires
Node.js 18+
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/b0r1sOm4g0/focus-todo-mcp
cd focus-todo-mcp
npm installRegister it with Claude Code; <YOUR_PATH_TO_FOCUS_TODO_MCP> is the full path of the folder you just cloned: claude mcp add --scope user focus-todo node "<YOUR_PATH_TO_FOCUS_TODO_MCP>/index.mjs"
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --scope user focus-todo node "<YOUR_PATH_TO_FOCUS_TODO_MCP>/index.mjs"<YOUR_PATH_TO_FOCUS_TODO_MCP> is the full path of the folder you cloned in the steps above.
