Time Tracking Billing Hours is answering right now. Last checked 10 min ago. It exposes 20 tools. Last commit 16 Oct 2026.
Billable-hours time tracking with rates and CSV export, running inside Claude or Cursor.
Uptime history
20 days of history
20 days agonow
100.0%
Uptime 24h
92 of 92 checks
20
Tools
read from the server
164 ms
Response time
average over 24h
2
Stars
last commit 16 Oct 2026
What changed 7
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 October 2026. No other catalogue keeps this.
15 Oct
6 tools appeared
entry_log, summary_client, summary_day and 3 more
15 Oct
a tool changed version
Nothing serious here today
Today is the operative word: we check Time Tracking Billing Hours every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.
run in your terminal
claude mcp add time-tracking-billing-hours --transport http https://mcp.zovo.one/mcp/time-tracking-billing-hours~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"time-tracking-billing-hours": {
"url": "https://mcp.zovo.one/mcp/time-tracking-billing-hours"
}
}
}~/.codex/config.toml
[mcp_servers.time-tracking-billing-hours]
url = "https://mcp.zovo.one/mcp/time-tracking-billing-hours".cursor/mcp.json
{
"mcpServers": {
"time-tracking-billing-hours": {
"url": "https://mcp.zovo.one/mcp/time-tracking-billing-hours"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"time-tracking-billing-hours": {
"url": "https://mcp.zovo.one/mcp/time-tracking-billing-hours"
}
}
}Available tools 20
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
entry
entry_add
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.
entry_delete
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.
entry_edit
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.
entry_list
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.
entry_log
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.
entry_mark_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.
summary
summary_client
All-time totals for one client/project: hours, entry count and billable amount, with a per-day breakdown.
summary_day
Total hours logged for one calendar day (local date, default today), broken down per project.
summary_week
Total hours logged in the week containing today (Mon-Sun, local dates), broken down per project.
timer
timer_start
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.
timer_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.
timer_stop
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.
license
license_activate
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.
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.
target
target_check
Compare hours logged this week (Mon-Sun, local dates) against the weekly target from target_set.
target_set
Set a weekly hours goal used by target_check. Stored locally.
export
export_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.
invoice
invoice_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.
project
project_set_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.
report
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.zovo.one/mcp/time-tracking-billing-hours | streamable-http | answering | 35 ms | 10 min ago |
Alternatives to Time Tracking Billing Hours
same job, measured the same wayTime Tracking
by theluckystrike
Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.
Timesheets
by theluckystrike
Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.
Time Tracker Timesheet Billable Hours
by theluckystrike
Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.
Timer Tracking
by theluckystrike
Timer and time-tracking add-on: start/stop timers, log entries, CSV export. Data stays local.
Timesheet
by theluckystrike
Timesheet from your AI chat: billable entries, weekly reports, CSV export. Local.
Mileage Log
by theluckystrike
Mileage log for deductible driving: trips, effective-dated rates, summaries and CSV export.
Kireo
by wang1051992187
Long-term memory for Claude Code, Cursor and any MCP client, with a searchable web dashboard.
Task tracking (sessions, ETA, dashboard)
by amineutron
Track long-running tasks in real time: sessions, steps, speed, ETA, HTTP API and TUI dashboard.
Time Tracking Billing Hours — questions
Answers built from our own checks of this server.
What can Time Tracking Billing Hours do?
It exposes 20 tools, read directly from the server on our last check. Among them: entry_add, entry_delete, entry_edit, entry_list, entry_log, entry_mark_billed and 14 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Time Tracking Billing Hours mostly used for?
Its tools cluster around entry, timer and summary. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Time Tracking Billing Hours working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 164 ms. The bar chart above shows every period we have measured.
How do I connect Time Tracking Billing Hours?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Time Tracking Billing Hours need an API key?
No. Time Tracking Billing Hours completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 20 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Time Tracking Billing Hours?
It answers our handshake in 164 ms on average, which is faster than 71% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Time Tracking Billing Hours open source?
Yes — it is published under the MIT licence, written in JavaScript and 2 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.