Clockify Time Tracking

What is Clockify Time Tracking?

Clockify Time Tracking is a Model Context Protocol (MCP) server that gives AI assistants access to the Clockify time-tracking API. It provides 112 tools across 18 domains for querying workspaces, projects, time entries, generating reports, logging hours, and managing clients, invoices, and more — all through natural language. The server is read‑only by default, with optional write operations behind an explicit opt‑in.

How to use Clockify Time Tracking?

Install via pip install clockify-mcp, run with uvx clockify-mcp, or use the Docker image. The easiest way with Claude Desktop is to download the prebuilt .mcpb bundle and double‑click it. Configure by setting CLOCKIFY_API_KEY in environment variables, a TOML config file at ~/.config/clockify-mcp/config.toml, or adding it to claude_desktop_config.json. Optionally set CLOCKIFY_ACCESS_MODE to time-tracking (log hours) or full (all writes).

Key features of Clockify Time Tracking

• 112 tools: 48 read‑only, 64 write (opt‑in) across 18 domains
• One‑click .mcpb installer for Claude Desktop
• Supports STDIO (default) and SSE/HTTP transports
• Configurable via environment variables or TOML file
• Access modes: read, time-tracking, full
• Scales to paid Clockify features (time off, holidays, invoices, etc.)

Use cases of Clockify Time Tracking

• Query workspaces, projects, and time entries in natural language
• Generate detailed, summary, weekly, attendance, or expense reports
• Log hours, create/update/delete time entries
• Manage clients, projects, tasks, tags, invoices, and expenses
• Approve time‑off requests, manage scheduling, and handle custom fields

FAQ from Clockify Time Tracking

How do I enable write operations?

Set the environment variable CLOCKIFY_ACCESS_MODE to time-tracking (only time‑entry writes) or full (all 64 write tools). The legacy CLOCKIFY_ENABLE_WRITES=true also works and maps to full.

What happens if I use a tool for a paid Clockify feature?

Tools for time off, holidays, expenses, approvals, custom fields, scheduling, invoices, and webhooks error with HTTP 402/403/404 on plans that don’t include those features.

How do I specify a workspace for a tool?

Most operations require a workspace ID. Tools accept an optional workspace_id parameter; if omitted they fall back to CLOCKIFY_DEFAULT_WORKSPACE_ID. If neither is set, the assistant will ask you to resolve one via list_workspaces.

Can I paginate through large lists?

List tools accept optional page and page_size parameters and return one page. High‑volume lists (list_time_entries, list_projects, etc.) also accept fetch_all=true to retrieve all pages concatenated.

What transport options does the server support?

The server runs on STDIO by default. Use --transport sse for SSE/HTTP. The streamable-http transport is also available. Note that SSE and HTTP have no built‑in authentication—only use them bound to loopback or behind an authenticated reverse proxy.