- Home
- MCP servers
- Clockify
Clockify
- javascript
4
GitHub Stars
javascript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"inakianduaga-clockify-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"CLOCKIFY_API_KEY=<YOUR_API_KEY>",
"ghcr.io/inakianduaga/clockify-mcp:latest"
],
"env": {
"CLOCKIFY_API_KEY": "<YOUR_API_KEY>"
}
}
}
}This Clockify MCP Server lets LLMs interact with your Clockify workspace to automate time-tracking tasks, run reports, and pull data across projects and users. It provides endpoint-like functionality so you can list projects, list users, add and view time entries, and generate summaries for custom date ranges, all integrated with your preferred MCP client.
How to use
You use the Clockify MCP Server by configuring it in your MCP client settings and starting the server as described. Once connected, you can perform operations such as listing projects, listing users, adding time entries, querying time entries for a user, and generating summary reports by user and project across a date range. The server is designed to work with LLMs to automate time-tracking workflows, generate summaries, and analyze your data across Clockify workspaces.
How to install
Prerequisites you need before starting:
-
Docker installed on your machine
-
A Clockify API key to access your workspace
How to install
{
"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": []
}
}
}
Additional configuration and usage notes
Obtain a Clockify API key from your Clockify account by generating a new key or copying your existing one. Use this key as the value for CLOCKIFY_API_KEY in the MCP server configuration.
Troubleshooting and tips
If you encounter issues connecting to Clockify, verify that your API key is correct and that the MCP server container can reach the Clockify API endpoints. Ensure the environment variable CLOCKIFY_API_KEY is provided in the server configuration and that the container is running with the proper privileges to access the network.
Notes on security and environment
Treat your Clockify API key as a sensitive credential. Do not share it publicly and use a dedicated key with appropriate permissions for automation tasks.
Tools exposed by the server
- 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
Available tools
listProjects
Fetch all projects accessible to the authenticated user in Clockify.
getTimeEntries
Retrieve time entries for the authenticated user with optional date filters.
addTimeEntry
Create new time entries for a project on behalf of a user you have permission to modify.
listUsers
List all users within the authenticated Clockify workspace.
getUserTimeEntries
Retrieve time entries for any user, subject to permissions, with optional date filters.
getSummaryReport
Obtain a summary of hours by user and project for a specified date range; supports monthly or custom ranges.