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.
Cursor is where the focus work happens, so the useful pattern is one sentence at the top of a session: plan 3 hours, then start block one — the agent can hold its own schedule without a separate timer app.
| 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.
The file is .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
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.
Cursor reads its own config, so here it is:
The config block:
{
"mcpServers": {
"pomodoro": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/pomodoro/dist/index.js"]
}
}
}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/pomodoroThat 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:
{
"mcpServers": {
"pomodoro": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-pomodoro"]
}
}
}The Customize page shows the server and its tools once it has started.
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.
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.
The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
Free: Everything: one tool, no metering, no key. Pro is $19 once, verified offline.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Pomodoro pasting the config block above is the supported route.
MCP Pomodoro in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs · Buy Pro