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.
Because mcp_config.json is loaded for every workspace, the timer follows you between projects, which is what you want from a tracker and not from a file tool. Eleven tools out of the 100 Cascade can hold is a cheap seat.
| 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 mcp_config.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| macOS, Windows and Linux | ~/.codeium/windsurf/mcp_config.json |
If you also run Claude Desktop, the shortest path there is one click: time-tracker.mcpb
from the bundle catalog opens as an extension, with no JSON and no terminal.
Windsurf reads its own config, so here it is:
The config block:
{
"mcpServers": {
"time-tracker": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/time-tracker/dist/index.js"]
}
}
}The node command above wants a built file. From a clone, once:
git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/time-trackerThat writes servers/time-tracker/dist/index.js, and its absolute path is the one argument
the config needs.
The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:
{
"mcpServers": {
"time-tracker": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-time-tracker"]
}
}
}Save and reopen the MCP Servers list; Cascade picks it up without restarting the editor.
Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the bundle catalog, a clone and build, or the hosted URL.
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>" }
}
}
}Read this first: mcp_config.json applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, takes its servers from the Devin CLI config files, so a correct entry here can still be invisible in a fresh tab. The other hard number is a cap: Cascade reaches at most 100 tools at once, and every enabled server spends from it.
Free: unlimited timers and entries, 7 days of reports, 2 rated projects. Pro is $19 once, verified offline.
~/.codeium/windsurf/mcp_config.json, under mcpServers. Reach it from the MCPs icon at the top right of the Cascade panel, or Devin Settings, Cascade, MCP Servers.
That file applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, reads its servers from the Devin CLI config files instead. Check which agent the tab runs.
Cascade reaches at most 100 tools at any one time, and every enabled server spends from that single budget. MCP Time Tracker contributes 13 tools, so keep the enabled list short rather than counting servers.
MCP Time Tracker in detail · The same server in VS Code and Cline · Every server in Windsurf · Guides · Windsurf docs · Buy Pro
How to track billable hours inside Claude Code and Cursor · Freelancer invoicing from chat: billable hours to invoice lines to PDF without a SaaS subscription · Run a kanban board in Claude, with time tracking on the same task · Is this project making money? Hours against costs, without a spreadsheet