
Pomodoro
io.github.theluckystrikePublished by GitHub account theluckystrikev1.0.1Updated Oct 24, 2026
Plan a workday into pomodoros, log focus sessions, get daily stats. All data is local.
Overview
Local MCP server that turns available minutes into a Pomodoro plan of 25-minute focus blocks, short breaks and a long break every fourth block.
- What you can do
- Plan a work session: split a given number of available minutes into 25-minute focus blocks with 5-minute short breaks and a 15-minute long break every fourth block.
- Adjust the plan: optionally specify a block count, and see where breaks fall and what time is left over.
- Handle partial windows: short or uneven windows are reported honestly, e.g. 40 minutes is not rounded up to a fake 50-minute pomodoro, and a 50-minute window returns one block plus one break.
- When to use it
- Useful when you plan your day inside an AI chat and want a concrete focus-and-break schedule for the time you have before a meeting or deadline, without opening a separate timer app. The plan can be pasted into a calendar or notes.
- Requirements
- Runs as a local stdio process on the user's machine (desktop only); the README shows an npx command or a Claude Desktop, VS Code or Cursor config entry. No account, API keys, environment variables or network calls are needed.
Installation
In SourceWeft
- Open Pomodoro in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
MCP Pomodoro — focus blocks planned in the chat you are already in
Turn "I have 3 hours before the demo" into a real pomodoro plan without opening a timer app. This MCP server gives Claude (or any MCP client) a pomodoro_plan tool that splits your available minutes into 25-minute focus blocks with 5-minute short breaks and a 15-minute long break every 4th block — the classic Pomodoro cadence, computed for your actual schedule instead of an app's default day.
Why a pomodoro server
Every pomodoro app asks you to plan around it: start a timer, reset it, keep the app open. If your work already happens inside an AI chat, the plan belongs there too. Ask for a plan in one sentence and paste it into your calendar, your notes, or just follow it on screen. No account, no telemetry, no network calls — the entire computation runs on your machine.
What it does
pomodoro_plan— given total minutes available (and optionally a block count), returns the session structure: how many 25-minute focus blocks, where the 5-minute breaks fall, when the 15-minute long break lands, and what is left over. Half-blocks are handled honestly: 40 minutes does not silently become a fake "50-minute pomodoro".- Works for short sessions too. A 50-minute window comes back as one focus block and one break, not an error.
Install
Or with the Claude Desktop / VS Code / Cursor config block above — one entry, one stdio server, no API keys.
Try it
- "I have 3 hours free this afternoon — plan it as pomodoros."
- "Plan my next 2 hours with breaks, I keep burning out without them."
- "How many focus blocks fit before my 4pm meeting?"
Part of the luckystrike MCP suite
Free, part of the luckystrike MCP suite — productivity & finance servers that turn AI chat into working documents and calculations. Listing in the official MCP Registry.
Docs (GitMCP)
Live docs endpoint: https://gitmcp.io/theluckystrike/mcp-pomodoro
Source: servers/pomodoro/README.md at commit 1bd9d69
Tools
0Version history
2- v1.0.1LatestOct 9, 2026
- v1.0.0Sep 27, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts