Popular servers: Spreadsheet · Server for Invoices — Generate Invoices from Claude · Expense Tracker — Log Expenses from Claude · Recurring Invoices · Word Document Server — Create .docx from Claude · Server for Bill of Sale — Draft and Sign from Claude · Zip · Job Card
The pomodoro technique dies in the tooling: the timer lives in one app, the log in another, and the invoice never hears about either. The MCP Time Tracker runs focus blocks in the same chat where the work is happening, so the timer, the log and the invoice lines share one source.
"Start a 25 minute focus block for the API refactor" starts the block and names the task. When it ends, the entry is logged automatically. After four blocks say "summarize today's focus sessions", and the day's pomodoros come back grouped by project, in hours and in money at your project rate.
Because every block is a timesheet entry from birth, there is no end-of-week reconstruction. The weekly billing guide picks up where this one ends: hours become invoice lines, and invoice lines become a PDF.
One click, with no JSON. Download time-tracker.mcpb from the
latest release and open it in Claude Desktop. It runs on the
Node runtime Claude Desktop ships with, so your own PATH and node version never come into it.
Or a URL, with nothing installed. /mcp/connect mints a free anonymous token and prints the ready line:
claude mcp add --transport http time-tracker https://mcp.zovo.one/mcp/time-tracker/t/<token>
Or from a clone, for a client with no bundle installer. Build once, then point the client at the built file:
git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/time-tracker
claude mcp add --scope user time-tracker -- node /absolute/path/to/mcp-servers/servers/time-tracker/dist/index.js
Claude Desktop, Cursor, Windsurf and Cline take the same two strings as JSON, in
claude_desktop_config.json or the client's own MCP config file:
{
"mcpServers": {
"time-tracker": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/time-tracker/dist/index.js"]
}
}
}
The npm packages are not published yet, so the npx form below returns a 404 today. It is
kept because it is what that config becomes the day the publish lands, with nothing else changed;
installing these servers when npx does not work yet
has the whole picture.
claude mcp add time-tracker -- npx -y @theluckystrike/mcp-time-tracker
No. It is the time tracker's timer with focus-block semantics, so sessions are ordinary timesheet entries and bill like one.
Yes. Ask for 25, 50 or any length in minutes; short and long breaks are just entries you choose not to bill.
Yes. Session entries carry the project rate, so the invoice summary turns a focus day into billed hours directly.
All MCP servers and prices · All guides · Buy the bundle $39