Track billable time without leaving the chat. It keeps a running timer, takes time you forgot to log, applies an hourly rate per project, and turns the log into a report, a CSV or invoice lines. Plain JSON on disk.
Cursor is where the billable hours are actually spent, so the useful pattern is to start the timer in the same chat you are about to ask for the refactor, and read the week back on Friday. Two rated projects on the free tier is usually two clients.
| You say | Tool |
|---|---|
| Start a timer for the Acme website project. | timer_start |
| Log 2.5 hours yesterday for Acme, design review, at 90 euros an hour. | entry_add |
| How many hours did I bill this month, grouped by project? | report |
In the audit run each of those sentences took one tool call, at 7.7 s and 14.6 s including a turn that also logged an expense.
The file is .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
{
"mcpServers": {
"time-tracker": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-time-tracker"]
}
}
}The Customize page shows the server and its tools once it has started.
The npm publish of @theluckystrike/mcp-time-tracker is pending; until then use the .mcpb bundle or a clone and build from the latest release.
The same server runs at https://mcp.zovo.one/mcp/time-tracker over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.
{
"mcpServers": {
"time-tracker": {
"url": "https://mcp.zovo.one/mcp/time-tracker",
"headers": { "Authorization": "Bearer <token>" }
}
}
}The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
Free: unlimited timers and entries, 7 days of reports, 2 rated projects. Pro is $19 once, verified offline.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Time Tracker pasting the config block above is the supported route.
MCP Time Tracker in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs