Pomodoro Timer MCP server
online · 100% uptimeio.github.theluckystrike/pomodoro-timer·v0.22.0·2 starsPomodoro work sessions from your AI chat: timed focus blocks, session logs.
2 stars
Reviews
Write oneNobody has reviewed Pomodoro Timer yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Pomodoro Timer tools (20, 1 write)
write = sends, deletes, buys or postsentry_addFreeLog 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_deletewrite actionFreeDelete 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_editFreeChange 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_listFreeList 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_logFreeLog 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_billedFreeClose 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.
export_csvFreeCall 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_summaryFreeTurn 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.
license_activateFreeTurn 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_statusFreeReport 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.
project_set_rateFreeSet 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.
reportFreeTimesheet 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.
summary_clientFreeAll-time totals for one client/project: hours, entry count and billable amount, with a per-day breakdown.
summary_dayFreeTotal hours logged for one calendar day (local date, default today), broken down per project.
summary_weekFreeTotal hours logged in the week containing today (Mon-Sun, local dates), broken down per project.
target_checkFreeCompare hours logged this week (Mon-Sun, local dates) against the weekly target from target_set.
target_setFreeSet a weekly hours goal used by target_check. Stored locally.
timer_startFreeStart 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_statusFreeReport 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_stopFreeStop 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.
Public scan report
scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- Live reliabilityremote reachable in 1969ms20/20
- Tool poisoning20 tool descriptions checked15/15
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Pomodoro Timer compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools
- 20
- the typical server has 7
- Tools that change things
- 5%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 10 ms
- faster than 98% of 30,031 servers
- GitHub stars
- 2
- more than 75% of 28,688 servers
What its tools let an agent do: 19 read · 1 change
Install Pomodoro Timer in Claude Code, Cursor or VS Code
claude mcp add --transport http pomodoro-timer https://mcp.zovo.one/mcp/pomodoro-timer
What the publisher says
From the Pomodoro Timer repository's README, as published. We do not edit it. Read it on GitHub
MCP servers by theluckystrike
<!-- gen:badge --> <!-- /gen:badge -->
Practical Model Context Protocol servers for people who work inside Claude, Cursor and other MCP clients. Every server runs locally over stdio, keeps all data on your machine, and has a genuinely useful free tier. Pro unlocks the limits for a one-time payment: $19 per server or $39 for the bundle, lifetime.
<!-- gen:counts --> 46 servers plus the office-suite aggregator, 45 of them also reachable as a hosted endpoint with no install. <!-- /gen:counts -->
No install? Use any server instantly as a hosted endpoint: https://mcp.zovo.one/mcp/ — or browse the catalog at mcp.zovo.one.
<!-- gen:install -->
That is the invoice server answering a real prompt: a client, some hours, a VAT rate, and a numbered PDF at the end. Every server in the table below has a demo like it.
Two ways to run any of these, both working today.
- One click. Download the server's .mcpb bundle from the latest release and open it in Claude Desktop. No terminal, no config file.
- No install at all. Point a client at https://mcp.zovo.one/mcp/. GET https://mcp.zovo.one/mcp/connect mints a free token and prints a ready URL for each server.
A third way is coming and does not work yet: the npm packages are unpublished, so npx -y @theluckystrike/mcp- returns 404 today. The commands below are written for the day it is published; use one of the two paths above until then. <!-- /gen:install -->
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Pomodoro Timer: common questions
- Is Pomodoro Timer MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Pomodoro Timer safety report
- How do I install Pomodoro Timer?
- It runs remotely at mcp.zovo.one. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Pomodoro Timer need an API key?
- Yes. The registry entry asks for
MCP_LICENSE_KEY,Authorization. - Is Pomodoro Timer maintained?
- The last commit was in the last day (2026-11-03). The latest release is v0.22.0.
- Is Pomodoro Timer up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Pomodoro Timer compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); tools 20 (the typical server has 7); tools that change things 5% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.