Clockify MCP server
Commit Nov 11, 2026Allows an AI client to list projects, log time in bulk, and manage time entries using your Clockify profile timezone.
Also known as condensetech/clockify-mcp-server
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 11, 2026
- License
- MIT
What is Clockify MCP?
Clockify allows an AI client to list projects, log time in bulk, and manage time entries using your Clockify profile timezone.
Summary generated from the project's README
About Clockify MCP server
Managing time tracking through natural language instead of clicking through a web interface is what this local stdio MCP server enables for Clockify users. Developers and freelancers can use an AI client to handle time logging tasks by providing simple text instructions. The server runs via npx and requires a Clockify API key provided through environment variables to function.
Users can interact with their data using specific tools like list_projects to see active work, log_time to create multiple entries at once, list_time_entries to review history, and delete_time_entries for removals. The system automatically handles time zone conversions by reading the settings from your Clockify profile, ensuring that a command like 09:00 matches your local time. It is a lightweight, single-file solution that operates entirely on your machine without hosting your credentials elsewhere.
What you can do with it
- 1Bulk time loggingInstruct your AI agent to create multiple time entries across different projects and days in a single request.
- 2Correcting mistakesTell the agent to remove a specific time entry that was logged incorrectly.
Written from the project's README. Every use case is checked against a quote from it.
Configuration
CLOCKIFY_API_KEY
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablecondensetech/clockify-mcp-server is public and reachablegithub.com/condensetech/clockify-mcp-server ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-11github.com/condensetech/clockify-mcp-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubclockify-mcp-server
Log time to your Clockify projects by asking your agent, instead of clicking through the UI.
"add 4h on ACME every morning this week and 4h on Evil Corp every afternoon"
→ one
log_timecall, 10 entries created, 40h total.
A local stdio MCP server. Run it with your own API key, nothing is shared or hosted. It
ships as a single file with no dependencies: a 140 kB download, so npx starts it in a
moment.
| Tool | What it does |
|---|---|
list_projects |
Active projects you can log time to |
log_time |
Create entries in bulk, project by name (and client if names repeat), date + start/end in your profile time zone |
list_time_entries |
Your time entries between two dates |
delete_time_entries |
Delete entries |
Times are in your Clockify profile time zone. You say 09:00, the server reads
settings.timeZone from your Clockify profile and converts to UTC.
Approval prompts come from your agent, not from this server. Whether you are asked
before each call is up to your harness and its permission settings. The server marks the
list_* tools read-only and delete_time_entries destructive, but these are
treated as hints: the server enforces no authorization of its own. Anything your API key
can do, the tools can too.
Use it 🚀
Everything you need if you just want to log time. Takes about two minutes.
1. Have Node 20 or later. Check with node --version.
2. Get your Clockify API key:
Clockify → your avatar → Preferences → ADVANCED tab → Manage API keys → GENERATE NEW
3. Register the server with your agent:
claude mcp add clockify -s user -e CLOCKIFY_API_KEY=<key> -- npx -y @condensetech/clockify-mcp-server@1
-s user writes it to your personal config so it loads in every project (the default
scope, local, would bind it to the current directory).
Add this to its MCP config:
{
"mcpServers": {
"clockify": {
"command": "npx",
"args": ["-y", "@condensetech/clockify-mcp-server@1"],
"env": { "CLOCKIFY_API_KEY": "<key>" }
}
}
}
Updates are automatic: each time your harness starts the server, npx fetches the
latest 1.x release. @1 also means a breaking 2.0 never reaches you unannounced.
4. Check it in a fresh session:
list my clockify projects
log 2 hours on <project> today from 09:00 to 11:00, description test
show my clockify entries for this week
delete that entry
Open the Clockify UI after the second prompt and confirm the entry reads 09:00–11:00. If it shows a different time, your Clockify profile time zone is not what you think it is, fix it in Clockify preferences.
Environment
| Variable | Required | Notes |
|---|---|---|
CLOCKIFY_API_KEY |
yes | Preferences → Advanced → Manage API keys |
CLOCKIFY_API_BASE |
no | Regional hosts: https://euc1.clockify.me/api/v1 (EU), euw2 (UK), use2 (US), apse2 (AU) |
Time is logged to your active workspace: the one selected in Clockify. To use another, switch to it in Clockify.
If something goes wrong
CLOCKIFY_API_KEY is not set— the key did not reach the server process. Put it in the harness config'senv, not in your shell.Ambiguous project "x". Candidates: …— deliberate. The server refuses to guess; use one of the listed names. Projects with the same name under different clients are listed asName (Client): name the client too, or pass the project id fromlist_projects.- 404s on every call — your workspace is on a regional host. Set
CLOCKIFY_API_BASE. - Entries land at the wrong hour — check your Clockify profile time zone (see step 4 of "Use it").
Contribute
Setup, checks and pull request rules are in CONTRIBUTING.md.
Clockify MCP questions
What happens if I have multiple projects with the same name?
The server will refuse to guess and will ask you to be more specific. You can provide the client name or the project ID.
Does the server require a specific API base URL?
By default, it uses the standard API, but if you are on a regional host (EU, UK, US, AU), you must set the CLOCKIFY_API_BASE environment variable.
Is my data shared with anyone?
No, it is a local stdio MCP server that runs with your own API key, so nothing is shared or hosted.