# Clockify Time Tracking MCP server

> Allows an AI assistant to query workspaces, projects, and time entries, generate reports, and manage clients, invoices, and expenses through natural language.

- Repository: https://github.com/tracegazer/clockify-mcp
- Page: https://hostedmcp.org/servers/tracegazer/clockify-mcp
- Transport: stdio
- Stars: 1
- License: MIT
- Latest version: 0.3.2

## Install

### Claude Code

```sh
claude mcp add --env 'CLOCKIFY_API_KEY=<YOUR_CLOCKIFY_API_KEY>' clockify-mcp -- uvx clockify-mcp
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "clockify-mcp": {
      "command": "uvx",
      "args": [
        "clockify-mcp"
      ],
      "env": {
        "CLOCKIFY_API_KEY": "<YOUR_CLOCKIFY_API_KEY>"
      }
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "clockify-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "clockify-mcp"
      ],
      "env": {
        "CLOCKIFY_API_KEY": "<YOUR_CLOCKIFY_API_KEY>"
      }
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"clockify-mcp","type":"stdio","command":"uvx","args":["clockify-mcp"],"env":{"CLOCKIFY_API_KEY":"<YOUR_CLOCKIFY_API_KEY>"}}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "clockify-mcp": {
      "command": "uvx",
      "args": [
        "clockify-mcp"
      ],
      "env": {
        "CLOCKIFY_API_KEY": "<YOUR_CLOCKIFY_API_KEY>"
      }
    }
  }
}
```

### Codex

```sh
codex mcp add clockify-mcp --env 'CLOCKIFY_API_KEY=<YOUR_CLOCKIFY_API_KEY>' --env 'CLOCKIFY_API_KEY=<YOUR_CLOCKIFY_API_KEY>' -- uvx clockify-mcp
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.clockify-mcp]
command = "uvx"
args = ["clockify-mcp"]

[mcp_servers.clockify-mcp.env]
CLOCKIFY_API_KEY = "<YOUR_CLOCKIFY_API_KEY>"
```

### Gemini CLI

```sh
gemini mcp add -s user -e 'CLOCKIFY_API_KEY=<YOUR_CLOCKIFY_API_KEY>' -e 'CLOCKIFY_API_KEY=<YOUR_CLOCKIFY_API_KEY>' clockify-mcp uvx -- clockify-mcp
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "clockify-mcp": {
      "command": "uvx",
      "args": [
        "clockify-mcp"
      ],
      "env": {
        "CLOCKIFY_API_KEY": "<YOUR_CLOCKIFY_API_KEY>"
      }
    }
  }
}
```

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `CLOCKIFY_API_KEY` | yes | yes | Clockify API key (Profile Settings -> API). |
| `CLOCKIFY_API_KEY` | yes | yes | Clockify API key (Profile Settings -> API). |
| `CLOCKIFY_ACCESS_MODE` | no | no | Write access mode: read (default, read-only) \| time-tracking (time-entry writes only) \| full (all writes) |
| `CLOCKIFY_ACCESS_MODE` | no | no | Write access mode: read (default, read-only) \| time-tracking (time-entry writes only) \| full (all writes) |
| `CLOCKIFY_DEFAULT_WORKSPACE_ID` | no | no | Default workspace id used when a tool call omits workspace_id. |
| `CLOCKIFY_DEFAULT_WORKSPACE_ID` | no | no | Default workspace id used when a tool call omits workspace_id. |
| `CLOCKIFY_TELEMETRY` | no | no |  |
| `OTEL_EXPORTER_OTLP_ENDPOINT` | no | no |  |
| `OTEL_EXPORTER_OTLP_HEADERS` | no | no |  |
| `OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE` | no | no |  |
| `OTEL_SERVICE_NAME` | no | no |  |

## FAQ

### Is the server read-only by default?

Yes, the server is read-only by default. You must explicitly opt-in to write operations using the CLOCKIFY_ACCESS_MODE configuration.

### How do I get my Clockify API key?

Log into your Clockify account, go to Profile Settings, select API, and copy your key.
