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 against Cascade's ceiling of 100 is the cheapest seat in this collection; the planner follows you between workspaces because mcp_config.json is loaded per workspace.
| 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 mcp_config.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| macOS, Windows and Linux | ~/.codeium/windsurf/mcp_config.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.
Windsurf reads its own config, so here it is:
The config block:
{
"mcpServers": {
"pomodoro": {
"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"]
}
}
}Save and reopen the MCP Servers list; Cascade picks it up without restarting the editor.
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.
Read this first: mcp_config.json applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, takes its servers from the Devin CLI config files, so a correct entry here can still be invisible in a fresh tab. The other hard number is a cap: Cascade reaches at most 100 tools at once, and every enabled server spends from it.
Free: Everything: one tool, no metering, no key. Pro is $19 once, verified offline.
~/.codeium/windsurf/mcp_config.json, under mcpServers. Reach it from the MCPs icon at the top right of the Cascade panel, or Devin Settings, Cascade, MCP Servers.
That file applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, reads its servers from the Devin CLI config files instead. Check which agent the tab runs.
Cascade reaches at most 100 tools at any one time, and every enabled server spends from that single budget. MCP Pomodoro contributes 1 tool, so keep the enabled list short rather than counting servers.
MCP Pomodoro in detail · The same server in VS Code and Cline · Every server in Windsurf · Guides · Windsurf docs · Buy Pro