Skip to main content
Glama

Build Status Docker Image

Clockify MCP Server

This MCP server allows LLMs (such as Cursor or Claude) to interact with your Clockify workspace, enabling advanced time-tracking automation and reporting. With this server, you can:

  • List all projects in your workspace

  • List all users in your workspace

  • Add and look up time entries for yourself or any user (if you have permissions)

  • Pull timesheets for any user across all projects

  • Generate monthly or custom date range breakdowns of hours by user and project using the Clockify summary report API

  • Integrate with LLMs to automate, summarize, or analyze your time-tracking data

Features

  • listProjects: List all projects for the authenticated user

  • getTimeEntries: List time entries for the authenticated user (with optional date filters)

  • addTimeEntry: Add time entries to a project

  • listUsers: List all users in the workspace

  • getUserTimeEntries: List time entries for any user (with optional date filters)

  • getSummaryReport: Get a summary report of hours by user/project for a date range (optionally filtered by userIds/projectIds). Enables monthly/hourly breakdowns for any user or project.

Related MCP server: clockify-mcp

Quick Start (Docker — Preferred)

MCP Server Configuration for Cursor/Claude

Add the following to your Cursor or Claude settings.json (replace YOUR_API_KEY):

{
  "mcpServers": {
    "clockify-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e", "CLOCKIFY_API_KEY=<YOUR_API_KEY>",
        "ghcr.io/inakianduaga/clockify-mcp:latest"  
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}

How to Obtain a Clockify API Key

  1. Log in to your Clockify account.

  2. Click on your profile icon (top right) and select Profile.

  3. Scroll down to the API section.

  4. Click Generate if you don't have an API key, or copy your existing key.

Contributing & CI/CD

This project uses GitHub Actions to automatically build and publish the Docker image to GitHub Container Registry (GHCR) on every push to main.

  • Image URL: ghcr.io/inakianduaga/clockify-mcp:latest

  • How to pull the image:

    docker pull ghcr.io/inakianduaga/clockify-mcp:latest

You can view published images in the "Packages" section of your GitHub profile or repository.

Memory Bank & Optimizations

Development has been done using cursor together with optimized rules. See: https://github.com/Bhartendu-Kumar/rules_template

License

This project is licensed under the MIT License. See the LICENSE file for details.

Available Tools

7 tools
addTimeEntryC

Add a time entry to a project.

Inputs: projectId (required), description (required), start (required), end (required).

getSummaryReportC

Get a summary report of hours by user/project for a date range. Optional: userIds, projectIds.

Inputs: start (required), end (required), userIds, projectIds.

getTimeEntriesC

List time entries for the authenticated user. Optional: start, end (ISO8601).

Inputs: start, end.

getUserTimeEntriesB

List time entries for a specified user. Optional: start, end (ISO8601).

Inputs: userId (required), start, end.

getUserTimeEntriesByNameB

List time entries for a user by name (case-insensitive, partial match allowed). Optional: start, end (ISO8601).

Inputs: userName (required), start, end.

listProjectsB

List all projects for the authenticated user.

Inputs: no named parameters.

listUsersB

List all users in the workspace.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 7 tools

    Disambiguation3/5

    Most tools have distinct purposes, but there is notable overlap between getTimeEntries, getUserTimeEntries, and getUserTimeEntriesByName, which all retrieve time entries with slight variations in filtering. This could cause confusion for an agent trying to select the right tool for listing time entries, as the boundaries between these three tools are not entirely clear.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern throughout, such as addTimeEntry, getSummaryReport, and listProjects. However, there is a minor deviation with getUserTimeEntriesByName, which includes an extra descriptor in the name, slightly breaking the pattern compared to the others.

    Tool Count5/5

    With 7 tools, the count is well-scoped for a time-tracking server like Clockify. Each tool serves a specific function in managing time entries, projects, and users, and none appear redundant or out of place for the domain.

    Completeness4/5

    The toolset covers core time-tracking operations well, including adding time entries, retrieving reports, and listing projects and users. However, there are minor gaps, such as no tools for updating or deleting time entries, which could limit full lifecycle management but are not critical for basic workflows.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers