mcpbeat Sign in

Clockify MCP by usefulapi MCP Server

answering

Clockify MCP by usefulapi is answering right now. Last checked moments ago. It exposes 21 tools. Last commit 10 Oct 2026.

Track time in Clockify: time entries, projects, clients, tags and reports; start, stop and log time.

Uptime history 47 hours of history
47 hours agonow
100.0%
Uptime 24h
92 of 92 checks
21
Tools
read from the server
108 ms
Response time
average over 24h
0
Stars
last commit 10 Oct 2026

Nothing serious here today

Today is the operative word: we check Clockify MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add clockify --transport http https://clockify.usefulapi.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "clockify": {
      "url": "https://clockify.usefulapi.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.clockify]
url = "https://clockify.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "clockify": {
      "url": "https://clockify.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "clockify": {
      "url": "https://clockify.usefulapi.io/mcp"
    }
  }
}

Available tools 21

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

clockify
clockify_create_client
WRITE: add a client to a workspace. POST /v1/workspaces/{workspaceId}/clients.
clockify_create_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_tag
WRITE: add a tag to a workspace. POST /v1/workspaces/{workspaceId}/tags.
clockify_create_task
WRITE: add a task to a project. POST /v1/workspaces/{workspaceId}/projects/{projectId}/tasks.
clockify_create_time_entry
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_delete_time_entry
WRITE (destructive): permanently delete one time entry. It cannot be undone. DELETE /v1/workspaces/{workspaceId}/time-entries/{id}.
clockify_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_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_get_project
One project by id: name, client, billable, color, note, estimate, duration tracked, rates and memberships. GET /v1/workspaces/{workspaceId}/projects/{projectId}.
clockify_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_get_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_list_clients
List the clients of a workspace (id, name, email, address, currency, archived). GET /v1/workspaces/{workspaceId}/clients.
clockify_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_list_tags
List the tags of a workspace (id, name, archived). GET /v1/workspaces/{workspaceId}/tags.
clockify_list_tasks
List the tasks of a project (id, name, status, assignees, estimate, duration tracked). GET /v1/workspaces/{workspaceId}/projects/{projectId}/tasks.
clockify_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_list_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_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_stop_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_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_update_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}.

Endpoints

URLTransportStateLatencyChecked
https://clockify.usefulapi.io/mcp streamable-http answering 107 ms 0 min ago

Alternatives to Clockify MCP by usefulapi

same job, measured the same way
Timen
by vahtel

Timen time tracking — timers, time entries, reports, projects, and clients.

answering
TrackingTime
by trackingtime

TrackingTime MCP server for time, projects, tasks, users, customers, services, and reports.

answering
Wufoo MCP by usefulapi
by usefulapi

Read forms, fields, entries, reports and comments by field title, and submit entries.

18 tools answering
FreeAgent MCP by usefulapi
by usefulapi

Read FreeAgent contacts, invoices, bills, banking and reports; add contacts, draft invoices, time.

20 tools answering
Persona MCP by usefulapi
by usefulapi

Read Persona inquiries, accounts, verifications and reports.

14 tools answering
Checkout.com MCP by usefulapi
by usefulapi

Read Checkout.com payments, disputes, reports and payouts.

18 tools answering
Codecov MCP by usefulapi
by usefulapi

Read Codecov coverage reports, commits, pulls, flags and components.

24 tools answering
Sendlane MCP by usefulapi
by usefulapi

Manage Sendlane lists, contacts, tags and custom fields; read campaign and SMS reports.

31 tools answering

Clockify MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Clockify MCP by usefulapi do?
It exposes 21 tools, read directly from the server on our last check. Among them: clockify_create_client, clockify_create_project, clockify_create_tag, clockify_create_task, clockify_create_time_entry, clockify_delete_time_entry and 15 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Clockify MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 108 ms. The bar chart above shows every period we have measured.
How do I connect Clockify MCP by usefulapi?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Clockify MCP by usefulapi need an API key?
No. Clockify MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 21 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Clockify MCP by usefulapi?
It answers our handshake in 108 ms on average, which is faster than 82% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Clockify MCP by usefulapi open source?
Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.