Home · Setup · Cline

MCP Pomodoro in Cline

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.

A single pure-compute tool with no side effects: put pomodoro_plan straight into the autoApprove array, there is nothing here a click would protect.

What you get in Cline

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 Cline

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

Scope	Path
Cline CLI	`~/.cline/mcp.json`
The editor extension	`opened from the Cline panel, not by path; the documentation deliberately calls it the MCP settings JSON used by the extension`

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. Cline 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"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

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:

{
  "mcpServers": {
    "pomodoro": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-pomodoro"]
    }
  }
}

No full-app restart. The MCP settings actions include restarting an unresponsive server if its tools do not appear.

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.

Cline notes worth knowing first

Cline is the one client here with an unsafe transport default. `type` selects it, and omitting `type` falls back to the legacy sse transport, so a streamable HTTP endpoint needs it written in or you will debug a server that is fine. Local entries carry "disabled" and an "autoApprove" array.

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

Questions

Where does the config live?

The CLI reads ~/.cline/mcp.json. For the extension, do not hunt for a path: MCP Servers icon, Configure tab, Configure MCP Servers. cline mcp opens a wizard, and cline config mcp --json is the non-interactive form.

The hosted endpoint will not connect.

Set the transport explicitly. Omitting type falls back to the legacy sse transport, so streamable HTTP needs "type": "streamableHttp" written in. It is the one default here that sends you debugging a server that works.

Should I auto-approve MCP Pomodoro's tools?

Approve the read-only ones and leave the writing ones behind a click: each entry carries an autoApprove array and a disabled flag.

MCP Pomodoro in detail · The same server in Windsurf and Claude.ai and Claude Desktop connectors · Every server in Cline · Guides · Cline docs · Buy Pro