CLI & MCP

Track time from your terminal — or hand it to your AI agent

WorkingClock ships a command-line client and a Model Context Protocol server. Script your hours in CI, or let Codex and Claude Code start timers and pull reports for you — all through the same API your account already uses.

Start tracking free Talk to us

zsh

$ workingclock start --project "Website redesign"
Started at 09:14:02.
$ workingclock status
▶ Website redesign · Homepage copy  00:42:11
$ workingclock stop
Stopped at 10:31:48. Logged 1h 17m.

The CLI and MCP server live in the WorkingClock repository and run from source today. Published npm packages — workingclock and workingclock-mcp — are on the way; this page shows the commands they will expose.

A CLI built for scripts and CI

Start and stop the same timer you see on web, mobile, and desktop. There is no client-side state — every command goes through the REST API, and every read command takes --json so it drops straight into a pipeline.

One running timer, everywhere
A timer you start in the terminal shows up live in the web, desktop, and mobile apps — and the other way around.
--json on every read
status, log, report, and the catalog commands emit clean JSON for jq, a dashboard, or a nightly cron.
Names, not UUIDs
--project "Website redesign" resolves against the API, so you never look up an id by hand.

zsh

$ workingclock login --email you@studio.com
Logged in. Active org: Acme Studio.
$ workingclock log --today --json
[
  {
    "project": "Website redesign",
    "task": "Homepage copy",
    "seconds": 4620,
    "billable": true
  }
]
$ workingclock report summary --from 2026-07-13 --to 2026-07-18
Total       18h 20m
Billable    18h 20m
Website redesign   12h 30m
API migration       5h 50m

mcp config

{
  "mcpServers": {
    "workingclock": {
      "command": "workingclock-mcp",
      "env": {
        "WORKINGCLOCK_API_BASE_URL": "https://api.workingclock.app",
        "WORKINGCLOCK_REFRESH_TOKEN": "wc_…",
        "WORKINGCLOCK_ORGANIZATION_ID": "org_…"
      }
    }
  }
}

An MCP server your AI agent can drive

The Model Context Protocol server exposes WorkingClock as tools an assistant can call. It is headless and stdio-based, authenticates from environment variables, and forwards your own token — so the agent only ever sees what you can see.

Tools the agent gets

Read — list projects, tasks, entries, and summary reports
Write — start, stop, create, update, and delete time entries
Every call is tenant- and permission-scoped by the backend; the server holds no elevated access

Works with Codex, Claude Code, and any MCP host

Point your assistant at the WorkingClock MCP server and track time the way you already work — in the same chat where you are writing code.

Things you can just ask

“Start a timer on Website redesign, task Homepage copy, and mark it billable.”

Started at 09:14. Running on Website redesign · Homepage copy, billable.

“How many billable hours did I log for Acme Inc. this week?”

18h 20m billable across 3 projects — Website redesign leads at 12h 30m.

“Stop whatever is running and show me today’s total.”

Stopped at 12:02. Today: 4h 52m across 5 entries.

Bring your hours into your workflow

Create a free account, then wire up the CLI or the MCP server against your own token.

Start tracking free