Enterprise DNAEnterprise DNA

MCP Servers

tracegazer/clockify-mcp

Full-coverage Clockify MCP — 112 tools across 18 domains (incl.

Our verdict

Not reviewed yet

We have not reviewed tracegazer/clockify-mcp yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About tracegazer/clockify-mcp

A Python-based MCP server that exposes 112 tools across 18 Clockify domains including invoices, scheduling, time-off, and approvals. It includes native OpenTelemetry observability and uses a three-tier access model for read, time-tracking, and full access.

Best for

Developers building AI assistants that need comprehensive Clockify integration

Use cases

  • Automating Clockify time entries and updates via AI agents
  • Querying Clockify reports and scheduling data through a model context protocol
  • Managing approvals and invoices with an AI assistant

Notes

0 stars on GitHub. Last updated 2026-06-09. Licensed MIT.

Pros

  • Covers nearly all Clockify domains with 112 tools for comprehensive integration
  • Built-in OpenTelemetry observability enables monitoring and debugging
  • Three-tier access model provides granular permission control

Cons

  • Requires a compatible MCP host environment to run
  • Large tool surface may be excessive for simple time-tracking needs
  • Performance depends on Clockify API availability and rate limits

Key facts

What we have checked

Days since the last commit
115
Checked GitHub
GitHub forks
1
Checked GitHub
GitHub stars
1
Checked GitHub
Open issues
0
Checked GitHub
Releases in the last 90 days
0
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Install

uvx clockify-mcp

Tools exposed

  • time-tracking
  • CLOCKIFY_API_KEY
  • CLOCKIFY_REGION
  • CLOCKIFY_BASE_URL
  • CLOCKIFY_DEFAULT_WORKSPACE_ID
  • CLOCKIFY_ACCESS_MODE
  • CLOCKIFY_ENABLE_WRITES
  • CLOCKIFY_TELEMETRY
  • CLOCKIFY_TELEMETRY_DETAIL

Clients the listing names (not checked here)

Claude Desktop

Install

Add tracegazer/clockify-mcp to your client

Not verified yet

Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.

Claude Code

Config checked

Run in your terminal (runs on your computer)

claude mcp add --env CLOCKIFY_API_KEY=YOUR_CLOCKIFY_API_KEY --transport stdio tracegazer-clockify-mcp -- uvx clockify-mcp@0.3.2

Needs CLOCKIFY_API_KEY: replace each YOUR_ value with your own.

Version 0.3.2 · From the Official MCP registry, read · Format checked against Claude Code's config docs

Claude Desktop

Config checked

Add to claude_desktop_config.json (runs on your computer)

{
  "mcpServers": {
    "tracegazer-clockify-mcp": {
      "command": "uvx",
      "args": [
        "clockify-mcp@0.3.2"
      ],
      "env": {
        "CLOCKIFY_API_KEY": "YOUR_CLOCKIFY_API_KEY"
      }
    }
  }
}

Needs CLOCKIFY_API_KEY: replace each YOUR_ value with your own.

Version 0.3.2 · From the Official MCP registry, read · Format checked against Claude Desktop's config docs

Cursor

Config checked

Add to .cursor/mcp.json (runs on your computer)

{
  "mcpServers": {
    "tracegazer-clockify-mcp": {
      "command": "uvx",
      "args": [
        "clockify-mcp@0.3.2"
      ],
      "env": {
        "CLOCKIFY_API_KEY": "YOUR_CLOCKIFY_API_KEY"
      }
    }
  }
}

Needs CLOCKIFY_API_KEY: replace each YOUR_ value with your own.

Version 0.3.2 · From the Official MCP registry, read · Format checked against Cursor's config docs

VS Code

Config checked

Add to .vscode/mcp.json (runs on your computer)

{
  "inputs": [
    {
      "type": "promptString",
      "id": "clockify-api-key",
      "description": "Clockify API key (Profile Settings -> API).",
      "password": true
    }
  ],
  "servers": {
    "tracegazer-clockify-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "clockify-mcp@0.3.2"
      ],
      "env": {
        "CLOCKIFY_API_KEY": "${input:clockify-api-key}"
      }
    }
  }
}

Needs CLOCKIFY_API_KEY: replace each YOUR_ value with your own.

Version 0.3.2 · From the Official MCP registry, read · Format checked against VS Code's config docs

Codex

Config checked

Add to ~/.codex/config.toml (runs on your computer)

[mcp_servers.tracegazer-clockify-mcp]
command = "uvx"
args = ["clockify-mcp@0.3.2"]
env_vars = ["CLOCKIFY_API_KEY"]

Needs CLOCKIFY_API_KEY: replace each YOUR_ value with your own.

Version 0.3.2 · From the Official MCP registry, read · Format checked against Codex's config docs

  • ChatGPT: ChatGPT connects only to remote servers that need no API key.

Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.

Works with

What tracegazer/clockify-mcp connects to

5 clients, each with how we know and when we checked.

Works withTypeHow we knowChecked
Claude CodeClientInstall recipe matches the client's documented formatRuns locally, version 0.3.2Config checkedClaude Code docs
Claude DesktopClientInstall recipe matches the client's documented formatRuns locally, version 0.3.2Config checkedClaude Desktop docs
CursorClientInstall recipe matches the client's documented formatRuns locally, version 0.3.2Config checkedCursor docs
VS CodeClientInstall recipe matches the client's documented formatRuns locally, version 0.3.2Config checkedVS Code docs
CodexClientInstall recipe matches the client's documented formatRuns locally, version 0.3.2Config checkedCodex docs

Stars and usage

How tracegazer/clockify-mcp is growing

GitHub stars

1 to 1

stars. 31 Oct 2026 to 13 Nov 2026, 3 readings.

Source: GitHub. Checked .

Health and security

Is tracegazer/clockify-mcp looked after, and what do its setup files show

Health score

28 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity22.4 of 30Last push 115 days ago
Releases0 of 150 releases in 90 days
Issue repliesNot countedThe latest check has no issue response reading (fewer than 3 measured issues, or issues switched off)
Maintainer0 of 15Owned by a single user
Official source0 of 20Community server

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Pairs with

Other entries in the index that connect to this one. Click through to see the chain.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.