Pomodoro Timer is answering right now. Last checked 14 min ago. It exposes 20 tools. Last commit 22 Oct 2026.
Pomodoro work sessions from your AI chat: timed focus blocks, session logs.
Uptime history
32 days of history · worst day 94%
32 days agonow
100.0%
Uptime 24h
87 of 87 checks
20
Tools
read from the server
221 ms
Response time
average over 24h
2
Stars
last commit 22 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
What the code does
We read the source, 2 d ago · tools taken from the live server · rules 995398eba69f
Capabilities
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
Hidden recipient in outgoing message
billing/src/index.js:1340
reply_to: "[email protected]" }),
Touches key and credential files
data/npm_unblock.json:34
"confound": "actions/setup-node with registry-url wrote NPM_CONFIG_USERCONFIG=$RUNNER_TEMP/.npmrc containing //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}; with no NODE_AUTH_TOKEN secret this expanded to the literal placeholder XXXXX-XXXXX-XXXXX-XXXXX, so npm authen…
Dumps the whole environment
servers/office-suite/src/index.ts:141
for (const [k, v] of Object.entries(process.env)) if (v !== undefined) env[k] = v;
Page loads a third-party script
telegram/public/index.html:11
<script src="https://telegram.org/js/telegram-web-app.js"></script>
Sends data to a third-party sink
telegram/src/bot.ts:205
console.error("Bot started; polling https://api.telegram.org");
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.
run in your terminal
claude mcp add pomodoro-timer --transport http https://mcp.zovo.one/mcp/pomodoro-timerSettings → Connectors → Add custom connector, then paste this address
https://mcp.zovo.one/mcp/pomodoro-timer~/.codex/config.toml
[mcp_servers.pomodoro-timer]
url = "https://mcp.zovo.one/mcp/pomodoro-timer".cursor/mcp.json
{
"mcpServers": {
"pomodoro-timer": {
"url": "https://mcp.zovo.one/mcp/pomodoro-timer"
}
}
}.vscode/mcp.json
{
"servers": {
"pomodoro-timer": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/pomodoro-timer"
}
}
}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/pomodoro-timer | streamable-http | answering | 841 ms | 14 min ago |
Alternatives to Pomodoro Timer
same job, measured the same wayPomodoro
by theluckystrike
Plan a workday into pomodoros, log focus sessions, get daily stats. All data is local.
Cairn
by cybort360
Log Claude Code work sessions, file edits, and tasks to your Cairn account.
Cronfy
by andreybroker
Time tracking you talk to: log, check and fix your work hours from your AI assistant.
Tallied
by withtallied
Log hours and invoice clients from your AI chat. Time tracking and invoicing for freelancers.
Emulo
by ohad6k
Mine your AI coding session logs into a you.md profile with dated receipts, for an agent to read.
redline
by gowtham0992
Run local prompt regression checks from prompt-response logs in AI coding assistants.
Agent Trading Journal
by smizxe
AI trading journal: your agent logs trades from chart screenshots and checks your own rules.
1lev1
by avi-adam
Track partnership work, log mission hours, and see what needs your approval on 1lev1.com.
Pomodoro Timer — questions
Answers built from our own checks of this server.
What can Pomodoro Timer 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 Pomodoro Timer mostly used for?
Its tools cluster around entry, summary and timer. 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 Pomodoro Timer working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 87 of 87 checks got a reply (100.0%), average response time 221 ms. The bar chart above shows every period we have measured.
How do I connect Pomodoro Timer?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Pomodoro Timer need an API key?
No. Pomodoro Timer 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 Pomodoro Timer?
It answers our handshake in 221 ms on average, which is faster than 64% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Pomodoro Timer open source?
The code is open source: it is published under the MIT licence, written in JavaScript and 2 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.zovo.one, which runs on its operator's own terms.