Home · Guides

Track billable time and export timesheets from your AI chat

Timesheet SaaS wants a seat fee and your team's discipline. The MCP Time Tracker runs in the chat you already have: start a timer when work starts, stop it when it ends, and the entry lands in a local log with the project name and any rate you set.

From timer to invoice

"Start a timer for client-acme", then "stop timer" is the whole loop. Backdated entries are first class ("Add 2.5 hours to client-acme yesterday, design review"), rates attach per project ("client-acme bills at 95/hour"), and "Weekly report" totals hours per project.

The export is a plain CSV you point at, ready for payroll or an accountant. Better: the invoice_summary tool hands tracked hours straight to the invoice generator, so tracked time becomes a numbered PDF invoice in one conversation. Local storage only, no account.

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

Questions

Where do entries live?

Locally, in a file the server owns. Exports publish only when you explicitly ask: publishing means writing a CSV you point at.

Can I invoice from this?

Yes. The invoice_summary tool turns tracked entries into lines for our invoice generator, so hours become a numbered PDF invoice in one step.

Is it free?

Full local tracking is free. Pro licensing covers team-scale use: see https://mcp.zovo.one/buy/pro.

All MCP servers and prices · All guides · Buy the bundle $39