Skip to content

Claude Desktop timer tracking timer_stop

How to: Claude Desktop timer tracking timer_stop

client:Claude Desktop transport:streamable-http tool:timer_stop

Add timer tracking to Claude Desktop

  1. 01

    Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "timer-tracking": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.zovo.one/mcp/timer-tracking"
      ]
    }
  }
}
  1. 02

    Save the file and restart Claude Desktop.

  2. 03

    Ask for something timer_stop does. Claude Desktop lists the server's tools on connect and calls timer_stop itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that timer tracking's identifier in your config matches the one above exactly.

Claude Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs

Set these first

timer tracking will not start until these are set, so timer_stop never becomes available.

  • MCP_LICENSE_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.