About Clockify MCP Server
Clockify MCP Server connects LLMs to a Clockify workspace for time-tracking operations and reporting. It supports entries, workspace users and projects, and date-range summaries.
Key features
- 01List workspace projects and users
- 02View and add time entries
- 03Retrieve users' timesheets
- 04Summarize hours by user and project
Use cases
- 01Recording project time through an LLM
- 02Reviewing a user's timesheet for a date range
- 03Preparing monthly or custom-period hour breakdowns
MCP support
It exposes Clockify project, user, time-entry, and summary-report operations as tools for MCP clients such as Cursor and Claude.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
docker run -i --rm -e CLOCKIFY_API_KEY ghcr.io/inakianduaga/clockify-mcp:latestCLOCKIFY_API_KEYSecretLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
ghcr.io/inakianduaga/clockify-mcp:lateststdioTools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEClockify 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.
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
- Log in to your Clockify account.
- Click on your profile icon (top right) and select Profile.
- Scroll down to the API section.
- 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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.