x=hub

your toolset

    build deployment
    sign in

    Clockify Time Tracking

    mcpkey · package
    io.github.tracegazer/clockify-mcp · v0.3.2
    deploy just this

    Clockify time-tracking MCP: 112 tools across 18 domains, read-only by default with opt-in writes.

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    #!/usr/bin/env bash
# clockify (io.github.tracegazer/clockify-mcp), recipe baremetal (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-clockify.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec uvx mcp-proxy --host 127.0.0.1 --port 8101 --pass-environment -- uvx clockify-mcp==0.3.2

[Unit]
Description=MCP server clockify (toolset my-agent), generated by Hub
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=mcp
Group=mcp
EnvironmentFile=/etc/mcp/my-agent.env
Environment=HOME=/var/lib/mcp/clockify
WorkingDirectory=/var/lib/mcp/clockify
ExecStart=/opt/mcp/my-agent/bin/clockify.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/clockify

[Install]
WantedBy=multi-user.target
    generated from the record, not tested yet
    docker run --rm -p 127.0.0.1:8101:8000 -e CLOCKIFY_API_KEY -e CLOCKIFY_ACCESS_MODE -e CLOCKIFY_DEFAULT_WORKSPACE_ID ghcr.io/astral-sh/uv:python3.12-bookworm-slim sh -c 'uvx mcp-proxy --host 0.0.0.0 --port 8000 --pass-environment -- uvx clockify-mcp==0.3.2'
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-18T00:08:18+00:00).
# Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
#   cp .env.example .env    # fill the ${VAR}s
#   docker compose up -d && bash smoke.sh
# Remote servers are not here: clients reach them directly (see clients/).
name: mcp-my-agent
services:
  clockify:
    image: ghcr.io/astral-sh/uv:python3.12-bookworm-slim
    command:
    - sh
    - -c
    - uvx mcp-proxy --host 0.0.0.0 --port 8000 --pass-environment -- uvx clockify-mcp==0.3.2
    ports:
    - 127.0.0.1:8101:8000
    volumes:
    - uv-cache:/root/.cache/uv
    healthcheck:
      test:
      - CMD
      - python3
      - -c
      - import urllib.request; urllib.request.urlopen('http://127.0.0.1:8000/status')
      interval: 30s
      timeout: 5s
      retries: 5
      start_period: 2m
    restart: unless-stopped
    environment:
      CLOCKIFY_API_KEY: ${CLOCKIFY_API_KEY}
      CLOCKIFY_ACCESS_MODE: ${CLOCKIFY_ACCESS_MODE}
      CLOCKIFY_DEFAULT_WORKSPACE_ID: ${CLOCKIFY_DEFAULT_WORKSPACE_ID}
volumes:
  npm-cache: {}
  uv-cache: {}
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-18T00:08:18+00:00).
#   kubectl create namespace mcp
#   kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
#   kubectl apply -f kubernetes.yaml
# Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
# with auth in front before exposing any of them.
apiVersion: v1
kind: Namespace
metadata:
  name: mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: clockify
  namespace: mcp
  labels: &id001
    app: clockify
spec:
  replicas: 1
  selector:
    matchLabels: *id001
  template:
    metadata:
      labels: *id001
    spec:
      containers:
      - name: clockify
        image: ghcr.io/astral-sh/uv:python3.12-bookworm-slim
        ports:
        - containerPort: 8000
          name: http
        env:
        - name: CLOCKIFY_API_KEY
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: CLOCKIFY_API_KEY
        - name: CLOCKIFY_ACCESS_MODE
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: CLOCKIFY_ACCESS_MODE
        - name: CLOCKIFY_DEFAULT_WORKSPACE_ID
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: CLOCKIFY_DEFAULT_WORKSPACE_ID
        command:
        - sh
        - -c
        - uvx mcp-proxy --host 0.0.0.0 --port 8000 --pass-environment -- uvx clockify-mcp==0.3.2
        readinessProbe:
          httpGet:
            path: /status
            port: http
          initialDelaySeconds: 10
---
apiVersion: v1
kind: Service
metadata:
  name: clockify
  namespace: mcp
spec:
  selector:
    app: clockify
  ports:
  - port: 8000
    targetPort: http
    name: http
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-18T00:08:18+00:00).
# Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
# Each server under `servers` is one Deployment + Service; the keys after it configure
# upstream charts a worker verified.
servers:
  clockify:
    enabled: true
    replicas: 1
    port: 8000
    path: /mcp
    container:
      name: clockify
      image: ghcr.io/astral-sh/uv:python3.12-bookworm-slim
      ports:
      - containerPort: 8000
        name: http
      env:
      - name: CLOCKIFY_API_KEY
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: CLOCKIFY_API_KEY
      - name: CLOCKIFY_ACCESS_MODE
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: CLOCKIFY_ACCESS_MODE
      - name: CLOCKIFY_DEFAULT_WORKSPACE_ID
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: CLOCKIFY_DEFAULT_WORKSPACE_ID
      command:
      - sh
      - -c
      - uvx mcp-proxy --host 0.0.0.0 --port 8000 --pass-environment -- uvx clockify-mcp==0.3.2
      readinessProbe:
        httpGet:
          path: /status
          port: http
        initialDelaySeconds: 10

# helm install my-agent helm/my-agent -n mcp

    in the cloud

    one click: the provider's deploy form opens filled in, in your own account
    koyeb
    deploy to koyeb

    The form opens with CHANGE_ME for each value you supply: CLOCKIFY_API_KEY, CLOCKIFY_ACCESS_MODE, CLOCKIFY_DEFAULT_WORKSPACE_ID. Fill them in before you deploy.

    Clients connect to the service's https://…koyeb.app address plus /mcp.

    azure
    deploy to azuretemplate

    A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.

    connect to it

    copy what your client needs
    uvx clockify-mcp==0.3.2
# env: CLOCKIFY_API_KEY, CLOCKIFY_ACCESS_MODE, CLOCKIFY_DEFAULT_WORKSPACE_ID
    {
  "mcpServers": {
    "clockify": {
      "command": "uvx",
      "args": [
        "clockify-mcp==0.3.2"
      ],
      "env": {
        "CLOCKIFY_API_KEY": "${CLOCKIFY_API_KEY}",
        "CLOCKIFY_ACCESS_MODE": "${CLOCKIFY_ACCESS_MODE}",
        "CLOCKIFY_DEFAULT_WORKSPACE_ID": "${CLOCKIFY_DEFAULT_WORKSPACE_ID}"
      }
    }
  }
}
    #!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add clockify -e "CLOCKIFY_API_KEY=${CLOCKIFY_API_KEY}" -e "CLOCKIFY_ACCESS_MODE=${CLOCKIFY_ACCESS_MODE}" -e "CLOCKIFY_DEFAULT_WORKSPACE_ID=${CLOCKIFY_DEFAULT_WORKSPACE_ID}" -- uvx clockify-mcp==0.3.2

    {
  "mcpServers": {
    "clockify": {
      "command": "uvx",
      "args": [
        "clockify-mcp==0.3.2"
      ],
      "env": {
        "CLOCKIFY_API_KEY": "${CLOCKIFY_API_KEY}",
        "CLOCKIFY_ACCESS_MODE": "${CLOCKIFY_ACCESS_MODE}",
        "CLOCKIFY_DEFAULT_WORKSPACE_ID": "${CLOCKIFY_DEFAULT_WORKSPACE_ID}"
      }
    }
  }
}
    {
  "servers": {
    "clockify": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "clockify-mcp==0.3.2"
      ],
      "env": {
        "CLOCKIFY_API_KEY": "${CLOCKIFY_API_KEY}",
        "CLOCKIFY_ACCESS_MODE": "${CLOCKIFY_ACCESS_MODE}",
        "CLOCKIFY_DEFAULT_WORKSPACE_ID": "${CLOCKIFY_DEFAULT_WORKSPACE_ID}"
      }
    }
  }
}
    name: my-agent
target: local
servers:
- hub: io.github.tracegazer/clockify-mcp
    • not probed yet: tools unpinned, ingest lists them

    tools

    Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.