io.github.theluckystrikePublished by GitHub account theluckystrikev0.22.0Updated Oct 24, 2026
Pomodoro work sessions from your AI chat: timed focus blocks, session logs.
A time-tracking server that lets an assistant run work timers, log hours per project, apply hourly rates and produce reports, CSV exports and invoice lines.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.theluckystrike%2Fpomodoro-timer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"pomodoro-timer": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/pomodoro-timer",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Featured on Awesome MCP Servers - directory listing | live hosted endpoint, free tier, no signup.
Track billable time without leaving your AI chat. Say "start a timer on the acme redesign", keep working, then ask for "my hours this week by project" or "invoice lines for acme in August". It keeps a running timer, lets you log time you forgot to track, applies your hourly rate per project, and turns the result into a report, a CSV file or a set of invoice line items. Everything is stored as plain JSON on your own machine.
Built by theluckystrike.
In the official MCP Registry (io.github.theluckystrike/time-tracker-timesheet-billable-hours).
Listed on the AI Product Index - live remote endpoint at mcp.zovo.one/s/time-tracker, free tier, no signup.
Track billable time from chat and turn it straight into a report or invoice line items, zero setup, all local.
npm publish for @theluckystrike/mcp-time-tracker is pending. Until then, the .mcpb one-click bundle or a clone+build
is the working path, both are verified below.
One-click (.mcpb): download time-tracker.mcpb from the latest release and double-click it in Claude Desktop:
https://github.com/theluckystrike/mcp-servers/releases/latest
(claude_desktop_config.json):
Claude Code:
(.cursor/mcp.json):
The npx form above starts working the moment the package is published. Until then, use the .mcpb bundle above, or
build from source with exactly these three commands:
Then point your client's command at node with one arg: the absolute path to servers/time-tracker/dist/index.js.
To run in Pro mode set MCP_LICENSE_KEY in the same config block, or call license_activate once with your key.
Also exposed: the resource timetracker://today (today's summary) and the prompt daily_standup
(writes a standup update from yesterday's and today's tracked time).
No tool names required. These are the sentences that were actually tested against the server; the tool column is what answered them.
Two more worth knowing: "export my time to a CSV for my bookkeeper" (export_csv) and "write my standup
update from yesterday and today" (the daily_standup prompt).
This is a real transcript from the audit in docs/USER_VALUE_R2.md, numbers unchanged.
One call each. The rate carries its currency all the way through: the report never prints a bare "225", and it never turns into "$225" by accident.
A second worked example, the weekly report and the daily_standup prompt:
An hour that has been invoiced is finished. entry_mark_billed {ids, invoice_number} writes
billed_at and billed_invoice onto those entries; from then on report and invoice_summary
skip them by default, so next month's "invoice Acme" cannot re-bill work already paid for. The
whole timesheet is still there: pass unbilled_only: false to any of them. invoice_summary
returns the entry_ids it used precisely so they can be handed straight to entry_mark_billed
once the invoice exists.
report and invoice_summary answer overlapping questions on purpose: report is for "how much time
and money," grouped any way you like; invoice_summary is for "give me the lines I can put on an
invoice," which is a narrower, invoice-shaped view of the same entries for one project.
Entries, projects and rates live in one JSON file:
${XDG_DATA_HOME:-~/.local/share}/mcp-servers/time-tracker/data.json.
Every write (starting or stopping a timer, adding, editing or deleting an entry, setting a rate) happens
under an advisory lock file at .../time-tracker/.lock, held across the whole load-mutate-save cycle, so
two overlapping calls cannot interleave and corrupt the file. The save itself writes to a temporary file
and renames it into place, so a crash or a killed process mid-write leaves either the old file or the new
one, never a half-written one. Reads (entry_list, report, timer_status, export_csv) do not take
the lock.
To back up your data, copy the single data.json file (and .lock if present, though it holds no data).
There is no database and no hidden second file.
If data.json is ever unreadable or not valid JSON, the server does not treat that as "no data yet".
It moves the file aside byte-for-byte as data.json.corrupt-<timestamp>, writes a data.json.corrupt
marker and makes every tool, reads included, return data file is corrupt; moved to ...; nothing was written. Restore a good data.json (the quarantined copy is right there) and delete the marker file to
carry on. Nothing is overwritten in the meantime.
2026-09-02T09:00:00 means 09:00 where you are, not
UTC. Pass an explicit offset (2026-09-02T09:00:00+02:00) or a trailing Z and it is honoured exactly.from: "2026-09-01" is 00:00:00 local on the 1st and
to: "2026-09-30" is 23:59:59.999 local on the 30th, so a month reported by dates includes its last
day. Timestamps with a time are used as given.from or ends after to counts for
the part inside the period, not all of it and not none of it.timer_status counts only the part of an
entry, or of the running timer, that falls after midnight today."1,200 USD" is 1200 (a comma followed by exactly three
digits is thousands grouping), "12,50 EUR" is 12.50 (the unambiguous European decimal shape), and
"1.200,50" is 1200.50. Anything that could mean either thing, such as "1,2345", is refused with a
worked example instead of being read as the wrong number.entry_add and timer_stop store the effective hourly
rate and currency on the entry, and reports and invoices use that stored rate. project_set_rate
therefore applies to future entries only; pass apply_to_existing: true to re-rate the time already
logged for that project. That re-stamps EVERY entry of the project, including entries that already
carry a rate, and the response says how many changed and the project's new total. Add
only_missing: true to touch only entries that captured no rate of their own.group_by: "tag" an entry tagged dev and meeting appears in both rows; the
total is computed from the entries once, so it is never the sum of the rows.entry_list, report, export_csv and invoice_summary only see the last 7 days. Timers and
entries themselves are unlimited and nothing is ever deleted, the window just narrows what a free
call can read back.report grouping is free, tag included: the tag total is a correctness fix, not a premium
feature. group_by itself is optional, omit it for the plain total per currency.npx hangs or fails to find the package: npm publish for this package is pending. Use the .mcpb
bundle or the clone-and-build path above until it lands..mcpb bundle: it installs into Claude Desktop directly; there is no separate path to
configure.servers/time-tracker/dist/index.js after
npm run build. Point your client's command at node with that absolute path as the only argument.node -v.--mcp-debug or check the terminal you launched it from.license_status to see what the server thinks your tier is, and
confirm MCP_LICENSE_KEY is set in the same process the client launches (not just your shell).All data stays local: entries live in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/time-tracker/data.json.
The server makes no network requests, has no telemetry, and needs no account. License keys are Ed25519
signatures verified offline against a public key compiled into the package, activation works with no
internet connection.
invoice_summary output straight into a numbered PDF invoice.export_csv and query or reshape it.Yes. All three speak MCP over stdio with the same config shape; the tools and the data file are identical regardless of client.
Nothing is deleted. The entry stays in data.json forever; it just will not appear in entry_list,
report, export_csv or invoice_summary results until you activate Pro, which opens full history.
Yes. Currency is set per project (or per entry, overriding the project default) and every total is grouped by currency, a report never adds EUR and USD together.
The server does not block overlaps; it logs what you tell it. entry_edit lets you fix a mistake after
the fact.
No. There are no network calls anywhere in this server, including for license activation, which is verified with a local public key.
MIT
Your identity is stored once, at ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/profile/business.json,
and every server in the suite reads it: the invoice issuer, the docx letterhead, the recurring
issuer, expense-tracker's default VAT rate, time-tracker's and timezone's home zone, and the
resume and contract letterheads. Set it once with business_set (invoice or docx) - you never
repeat it anywhere else. An email address is only ever taken from that profile or from an explicit
argument; when none is stored, documents show [add: email] and the tool says so rather than
letting anyone improvise an address.
Yes. The time-tracker server at mcp.zovo.one is a free MCP time tracking server with no install: start and stop timers in chat, keep per-client totals, and produce weekly reports. Unlike SaaS trackers (WebWork, TrackingTime) it needs no account - paste the hosted URL and go.
Connect https://mcp.zovo.one/mcp/time-tracker (tokenized URL from mcp.zovo.one/mcp/connect) and say: 'Start a timer for the Acme project.' Stop it later the same way; weekly summaries are one ask away.
Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:
Source: servers/time-tracker/README.md at commit 55b3f42
License status
Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.
Takes no parameters.
Activate license
Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.
keyrequiredStart timer
Start a stopwatch for work on a project and return the start time. Only one runs at a time: a new one stops and logs the previous, naming it. rate is an hourly rate in MAJOR units for this timer only.
ratetagstaskprojectrequiredcurrencyStop timer
Stop the running timer and log it as one entry. Returns the duration, the money at the rate in force and the new entry id. With no timer running it says so and writes nothing.
noteTimer status
Report the running timer and today's total hours. Today is the local calendar day, so a timer started at 23:30 yesterday contributes only the minutes since midnight. No arguments, and it writes nothing.
Takes no parameters.
Add time entry
Log time already worked as one entry and return its id, duration and amount. Give start plus end or minutes. rate is hourly in MAJOR units and is frozen on the entry, so a later rate change never moves it.
endnoteratetagstaskstartrequiredminutesprojectrequiredbillablecurrencyLog work time
Log work time for a client/project in one step: minutes worked plus an optional note. The entry starts now minus the minutes, so it lands on today's day and week summaries.
noteclientrequiredminutesrequiredprojectDaily summary
Total hours logged for one calendar day (local date, default today), broken down per project.
dateWeekly summary
Total hours logged in the week containing today (Mon-Sun, local dates), broken down per project.
Takes no parameters.
Client summary
All-time totals for one client/project: hours, entry count and billable amount, with a per-day breakdown.
clientrequiredSet weekly hours goal
Set a weekly hours goal used by target_check. Stored locally.
weekly_hoursrequiredCheck weekly hours goal
Compare hours logged this week (Mon-Sun, local dates) against the weekly target from target_set.
Takes no parameters.
List time entries
List logged entries as a table of id, day, start, project, task, hours, billable, tags and note, newest first, with total hours. Free reads the last 7 days and says so; Pro reads the whole history.
tofromlimitprojectDelete time entry
Delete one logged entry by id and report the project and hours removed. It never touches a running timer. A billed entry goes too, losing the invoice record, so correct one with entry_edit instead.
idrequiredEdit time entry
Change one logged entry by id; only the fields you pass move. minutes keeps start and moves end, an end at or before start is refused, tags REPLACES the list, and rate is hourly in MAJOR units.
idrequiredendnoteratetagstaskstartminutesprojectbillablecurrencySet project rate
Set the hourly rate and currency used to turn tracked hours into money for a project or client. Returns the new rate and, when re-rating is asked for, how many already logged entries changed.
projectrequiredcurrencyhourly_raterequiredonly_missingapply_to_existingTime report
Timesheet report: total tracked hours and billable money for a period, optionally grouped by (group by) project, day, task or tag - hours per project, how much to bill. Omit group_by for the plain total per currency.
torequiredfromrequiredformatprojectgroup_byunbilled_onlyExport entries to CSV
Call this tool to export the timesheet to a CSV file (excel-friendly) you can hand to a bookkeeper: one row per entry with hours, billable, rate, currency and amount. Returns the file path written.
tofrompathprojectMark time entries as billed
Close the loop after an invoice is issued: stamp the tracked hours that went on it with the invoice number, so report and invoice_summary stop offering them and the same hours are never billed twice.
toidsfromprojectbilled_atinvoice_numberrequiredInvoice summary
Turn tracked billable time into invoice lines for one project: hours, hourly rate, amount per task and the total, one line per rate so two rates never average. Hours already marked billed are left out. Free: last 7 days.
torequiredfromrequiredprojectrequiredunbilled_only100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
{ "mcpServers": { "time-tracker": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-time-tracker"] } }}claude mcp add time-tracker -- npx -y @theluckystrike/mcp-time-tracker{ "mcpServers": { "time-tracker": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-time-tracker"] } }}git clone https://github.com/theluckystrike/mcp-servers.git && cd mcp-serversnpm installnpm run build -w packages/mcp-license -w servers/time-trackerYou: Log 2.5 hours yesterday for Acme, design review, at 90 euros an hour.
entry_add { project: "Acme", ... } -> "Acme" resolved to the existing project "Acme website" -> rate "90 euros an hour" parsed as EUR 90.00/h
Assistant: Logged 2.50 h for Acme website - design review at EUR 90.00/h = EUR 225.00.
You: How much do I bill Acme this week? Give me invoice lines.
invoice_summary { project: "Acme website", from: "2026-08-31", to: "2026-09-02" }
Assistant: Invoice summary - Acme website design review 2.50 h EUR 90.00/h EUR 225.00 TOTAL 2.50 h EUR 225.00You: How many hours did I put into Acme this week, grouped by task?
report { project: "Acme website", from: "2026-08-27", to: "2026-09-02", group_by: "task" }
Assistant: Acme website, 2026-08-27 to 2026-09-02 design review 2.50 h EUR 225.00 TOTAL 2.50 h EUR 225.00
You: Write my standup update.
(prompt) daily_standup
Assistant: Yesterday: 2.50 h on Acme website (design review).Today: nothing logged yet.