Track time in Clockify: time entries, projects, clients, tags and reports; start, stop and log time. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"clockify": {
"url": "https://clockify.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"clockify": {
"type": "http",
"url": "https://clockify.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Clockify API key and Data region.
Optional: Workspace subdomain (only for a regional workspace on its own subdomain).
Create the key in Clockify → Profile settings → Advanced → Manage API keys → Generate new. The key acts with your permissions in each workspace. The data region is shown in Workspace settings; most workspaces are Global. A workspace on its own subdomain (acme.clockify.me) needs a key generated while you are in that workspace. Your key is used only to call the Clockify API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Clockify API key and Data region. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
clockify_get_current_user | read | Get current user The Clockify user this API key belongs to: id, name, email, status, active and default workspace ids, and profile settings (time zone, week start, date/time format). GET /v1/user. |
clockify_list_workspaces | read | List workspaces List the Clockify workspaces you belong to: id, name, plan (featureSubscriptionType), subdomain, currencies and default hourly/cost rate. Use the id as workspace_id in other tools. GET /v1/workspaces. |
clockify_list_users | read | List workspace users List the members of a workspace: id, name, email, status and settings. Filter by name, email, status or project access. GET /v1/workspaces/{workspaceId}/users. |
clockify_list_clients | read | List clients List the clients of a workspace (id, name, email, address, currency, archived). GET /v1/workspaces/{workspaceId}/clients. |
clockify_list_projects | read | List projects List the projects of a workspace: id, name, client, billable, public, color, archived, duration tracked, estimate and rates. Filter by name, client, user, billable or archived. GET /v1/workspaces/{workspaceId}/projects. |
clockify_get_project | read | Get a project One project by id: name, client, billable, color, note, estimate, duration tracked, rates and memberships. GET /v1/workspaces/{workspaceId}/projects/{projectId}. |
clockify_list_tasks | read | List project tasks List the tasks of a project (id, name, status, assignees, estimate, duration tracked). GET /v1/workspaces/{workspaceId}/projects/{projectId}/tasks. |
clockify_list_tags | read | List tags List the tags of a workspace (id, name, archived). GET /v1/workspaces/{workspaceId}/tags. |
clockify_list_time_entries | read | List time entries List the time entries of one user (default: you), newest first: id, description, project, task, tags, billable and timeInterval (start, end, ISO 8601 duration). Filter by time range, project, task, tags or description. For totals across users use clockify_summary_report. GET /v1/workspaces/{workspaceId}/user/{userId}/time-entries. |
clockify_get_time_entry | read | Get a time entry One time entry by id: description, project, task, tags, billable, rates, custom fields and timeInterval. GET /v1/workspaces/{workspaceId}/time-entries/{id}. |
clockify_get_running_timer | read | Get running timer The timer that is running right now for a user (default: you), or running: false. GET /v1/workspaces/{workspaceId}/user/{userId}/time-entries?in-progress=true. |
clockify_summary_report | read | Summary report Totals of tracked time (seconds) and amounts for a date range across the workspace, grouped by up to 3 levels (default project → time entry), e.g. hours per user per project last month. Respects the filters. POST reports /v1/workspaces/{workspaceId}/reports/summary. |
clockify_detailed_report | read | Detailed report Every time entry in a date range across the workspace (user, project, client, task, tags, description, start/end, duration in seconds, amount), with totals; newest first, paged. POST reports /v1/workspaces/{workspaceId}/reports/detailed. |
clockify_create_time_entry | write | Log time or start a timer WRITE: add a time entry for yourself. With end = a finished entry (log time); without end = a running timer that starts at start (default now). A workspace with required custom fields may refuse it. POST /v1/workspaces/{workspaceId}/time-entries. |
clockify_stop_timer | write | Stop running timer WRITE: stop the running timer of a user (default: you) at end (default now). Clockify answers 404 if no timer is running. PATCH /v1/workspaces/{workspaceId}/user/{userId}/time-entries. |
clockify_update_time_entry | write | Update a time entry WRITE: change a time entry's start, end, description, project, task, tags or billable. Only the fields you pass change: the entry is read first and every other field (custom fields included) is sent back as it was. The entry is rewritten (PUT) from a fresh read, so an edit made to the same entry in between (e.g. in the Clockify app) can be lost. A new project without task_id clears the task. GET then PUT /v1/workspaces/{workspaceId}/time-entries/{id}. |
clockify_delete_time_entry | write | Delete a time entry WRITE (destructive): permanently delete one time entry. It cannot be undone. DELETE /v1/workspaces/{workspaceId}/time-entries/{id}. |
clockify_create_project | write | Create a project WRITE: create a project in a workspace (needs an admin or project-manager role, depending on workspace settings). POST /v1/workspaces/{workspaceId}/projects. |
clockify_create_task | write | Create a task WRITE: add a task to a project. POST /v1/workspaces/{workspaceId}/projects/{projectId}/tasks. |
clockify_create_client | write | Create a client WRITE: add a client to a workspace. POST /v1/workspaces/{workspaceId}/clients. |
clockify_create_tag | write | Create a tag WRITE: add a tag to a workspace. POST /v1/workspaces/{workspaceId}/tags. |
clockify_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
clockify_request_feature | Request a missing feature Tell usefulapi that the user needs something the Clockify tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
clockify_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Clockify tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
clockify_cancel_subscription | Cancel the Pro subscription Cancel the caller's Clockify Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run clockify_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this Clockify server only. Subscribe with clockify_upgrade (it returns a Stripe Checkout link). Cancel any time with clockify_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running clockify_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Clockify. The server calls the Clockify API with your own Clockify access, so it sees only the data that your account can see.
The login page asks for your Clockify API key and Data region. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Clockify API key and Data region. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Clockify API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Clockify.
Yes, if you approve it. 8 of the 21 Clockify tools can create or change data. The other 13 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Clockify server only. Run clockify_usage_status to see how many calls you used.
Ask the AI to run clockify_upgrade: it returns a Stripe Checkout link. To cancel, run clockify_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with clockify_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.