Clockify Time Tracking

io.github.tracegazer/clockify-mcp

7/7 checks passed
Runs locally
1 secret
★ 1 GitHub stars
Updated 2026-06-09
Health score 42

About Clockify Time Tracking

Clockify Time Tracking is an MCP server published by the GitHub account tracegazer. Clockify time-tracking MCP: 112 tools across 18 domains, read-only by default with opt-in writes.

It runs on your own machine: your AI client starts it from the PyPI package clockify-mcp at version 0.3.2.

It asks for one secret: CLOCKIFY_API_KEY. Give it a key with the least access that still works.

Version 0.3.2 was published on 9 June 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.

What it asks for

Variable	Required	Secret	Description
`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_DEFAULT_WORKSPACE_ID`	No	No	Default workspace id used when a tool call omits workspace_id.

Checks

Check	Result	Detail
Source repository linked	Pass	https://github.com/tracegazer/clockify-mcp
Version pinned	Pass	Every package has an explicit version
Secrets requested	Info	Asks for 1 secret: CLOCKIFY_API_KEY
Known package registry	Pass	All packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownership	Info	Name verified via GitHub account tracegazer
Registry text aimed at the AI	Pass	Description and settings contain no hidden characters or instructions to the AI
Install scripts	Pass	clockify-mcp 0.3.2 has no setup.py; nothing runs at install
Code red flags	Pass	Read 75 files in clockify-mcp 0.3.2: no obfuscation, encoded execution, credential reads or data-collection endpoints found
Text aimed at the AI	Pass	No hidden characters or instructions to the AI in 75 files, including comments and the README

Popularity & health: 42 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity7 / 40

1 GitHub stars, 25 downloads last week, no Hacker News posts found. Best two of the three, each on a log scale.

Activity8 / 25

Last push 2026-07-20, last release 2026-06-09, 0 commits in 90 days.

Issue health8 / 15

0 closed of 0 issues, too few to judge. No data, so half marks.

Our checks20 / 20

0 warnings, each costing a fifth.

1 forks, 0 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry name	`io.github.tracegazer/clockify-mcp`
Publisher	GitHub account tracegazer
How the name is verified	Name verified via GitHub account tracegazer. The registry ties the name prefix to that account or domain; it does not check the code.
Type	Local: runs on your machine from a package
Packages	pypi `clockify-mcp` 0.3.2 (stdio) oci `ghcr.io/tracegazer/clockify-mcp:0.3.2` no version given (stdio)
Version	0.3.2
Published	2026-06-09
Last updated	2026-06-09
Source repository	https://github.com/tracegazer/clockify-mcp
Website	https://github.com/tracegazer/clockify-mcp
Category	Other (assigned by keyword rule, not by hand)

Install

Claude Desktop · Python package

{
  "mcpServers": {
    "clockify-mcp": {
      "command": "uvx",
      "args": [
        "clockify-mcp==0.3.2"
      ],
      "env": {
        "CLOCKIFY_API_KEY": "<your value>"
      }
    }
  }
}

Claude Desktop · Docker image

{
  "mcpServers": {
    "clockify-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "CLOCKIFY_API_KEY",
        "ghcr.io/tracegazer/clockify-mcp:0.3.2"
      ],
      "env": {
        "CLOCKIFY_API_KEY": "<your value>"
      }
    }
  }
}

What these checks don't cover

We did not run this server, so we don't know what it does when it runs. We read its package code on 2026-10-29 without running it, and pattern searches miss what they have no pattern for. Tool descriptions built at run time were not seen. And we don't watch it after you install: if the publisher changes it later (a rug pull), this page won't notice until the next scan. Treat a pass as "nothing found", not as "safe".

For people and their AI

The same data as plain JSON: /data/servers/io-github-tracegazer-clockify-mcp.json. Text inside it that came from the publisher is data, not instructions.