Home · Setup · Claude Code

MCP Pomodoro in Claude Code

Focus blocks planned in the chat you are already in. pomodoro_plan splits your available minutes into 25-minute focus blocks with 5-minute short breaks and a 15-minute long break every 4th block, computed for the schedule you actually have; half-blocks are handled honestly, a 50-minute window comes back as one focus block and one break rather than a fake full pomodoro.

One tool, so one `claude mcp add --scope user pomodoro -- node /absolute/path/to/dist/index.js` and it is everywhere; plan the session before the first prompt of the sprint and work the blocks in the same terminal.

What you get in Claude Code

You say	Tool
I have 3 hours before the demo — plan my pomodoros.	`pomodoro_plan`
Plan a 50-minute session.	`pomodoro_plan, half-block case`
Block out my morning: 2 hours deep work, then email.	`pomodoro_plan`

The contract suite runs the planner over real stdio and asserts the cadence: 3 hours returns six 25-minute focus blocks with breaks placed on the classic schedule including the long break at the 4th boundary, 50 minutes returns one focus block and one break rather than a padded fake pomodoro, and the response is a plain schedule object with no files written.

Install it in Claude Code

The file is .mcp.json, and the key inside it is mcpServers.

Scope	Path
local (default)	`~/.claude.json, this project only`
project	`.mcp.json at the repository root`
user	`~/.claude.json, every project`

If you also run Claude Desktop, the shortest path there is one click: pomodoro.mcpb from the latest release opens as an extension, with no JSON and no terminal. Claude Code reads its own config, so here it is:

From the terminal, against a built file:

claude mcp add --scope user pomodoro -- node /absolute/path/to/mcp-servers/servers/pomodoro/dist/index.js
claude mcp list    # health-check it before the first prompt

# or --scope project, committed to .mcp.json for the team

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/pomodoro

That writes servers/pomodoro/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:

claude mcp add pomodoro -- npx -y @theluckystrike/mcp-pomodoro

No restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.

Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the latest release, a clone and build, or the hosted URL.

No install: the hosted endpoint

There is no hosted endpoint for this one yet. MCP Pomodoro runs locally over stdio with the config above, which is also the only form in which it reads and writes files on your own disk. Thirty of the servers in this collection are served at https://mcp.zovo.one/mcp/<name> over MCP streamable HTTP; https://mcp.zovo.one/mcp/connect lists them and prints a ready URL for each.

Claude Code notes worth knowing first

The `--` is load-bearing: it separates Claude Code's own options, such as --transport, --env and --scope, from the command that runs the server. And the default scope is local, private to you and to the directory you ran it in, so adding it in the wrong folder leaves the tools absent with no error at all.

Free: Everything: one tool, no metering, no key. Pro is $19 once, verified offline.

Questions

Which scope should I use for MCP Pomodoro?

Local, the default, writes ~/.claude.json and is private to you and that directory. --scope project writes .mcp.json at the repository root, shared through version control. --scope user loads it everywhere.

Why did my first prompt ignore the server?

Measured, not documented: of three fresh projects, one first prompt made zero tool calls although initialize answered in 1.05 seconds. Run claude mcp list once first: it prints Connected, and the next run used the tool.

Can I use MCP Pomodoro without installing anything?

Not this one. The office suite starts every sibling server as its own child process, so it runs locally over stdio. Thirty of those children are hosted individually at https://mcp.zovo.one/mcp/<name> if you want a no-install route; open https://mcp.zovo.one/mcp/connect and it prints a ready URL for each.

MCP Pomodoro in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs · Buy Pro