Time Tracking Billing Hours

Track time from Claude with a free, no-install server

Featured on [Awesome MCP Servers](https://mcpservers.org) - 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](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.theluckystrike%2Ftime-tracker-timesheet-billable-hours/versions/latest) (io.github.theluckystrike/time-tracker-timesheet-billable-hours).

Listed on the [AI Product Index](https://index.percall.dev/l/zovo-time-tracker.html) - 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.

60-second install

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):

{

"mcpServers": { "time-tracker": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-time-tracker"] } } }

Claude Code:

claude mcp add time-tracker -- npx -y @theluckystrike/mcp-time-tracker

(.cursor/mcp.json):

{

"mcpServers": { "time-tracker": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-time-tracker"] } } }

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:

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

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.

Tools

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).

What you can say

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).

Worked example

This is a real transcript from the audit in docs/USER_VALUE_R2.md, numbers unchanged.

You: 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.00

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:

You: 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.

Billed hours close

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.

How it stores data

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- , 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.

Dates, times and rates

• Timestamps with no offset are your local time. 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.
• Date-only bounds cover whole local days. 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.
• Entries are clipped to the window. An entry that starts before from or ends after to counts for the part inside the period, not all of it and not none of it.
• Entries are split at local midnight for day grouping. Work from 23:30 to 01:30 is 0.5 h on the first day and 1.5 h on the next, including across a month boundary. timer_status counts only the part of an entry, or of the running timer, that falls after midnight today.
• Rate strings are parsed, never guessed. "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.
• Rates are captured when the time is logged. 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.
• Tag rows overlap. In 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.

Limits and honest caveats

• Free entry_list, report, export_csv and invoice_summary only see the last 7 days. T