# Clockify Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Clockify

Track time, projects, clients and tags; start, stop and log time entries; generate reports.

- Record: https://musedirectory.ai/connector/clockify
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/clockify/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 219ms, checked 2026-10-29T11:31:05Z
- Endpoint: https://clockify.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T07:56:29Z)
- Source: Found in the official MCP Registry (io.usefulapi/clockify) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fclockify

Connect to Clockify time tracking. Start and stop timers, log time entries, organize work by projects, clients and tags, and generate summary and detailed reports of tracked time and billable amounts.

Example request: "Start a timer for the project I'm working on right now and tag it as billable."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Clockify to help me. It is a free service with an MCP server at https://clockify.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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_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: 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: 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_get_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: List the tasks of a project (id, name, status, assignees, estimate, duration tracked). GET /v1/workspaces/{workspaceId}/projects/{projectId}/tasks.
- clockify_list_tags: List the tags of a workspace (id, name, archived). GET /v1/workspaces/{workspaceId}/tags.
- 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/
- 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_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: 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: 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: 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 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: 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 t
- clockify_delete_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 in a workspace (needs an admin or project-manager role, depending on workspace settings). POST /v1/workspaces/{workspaceId}/projects.
- clockify_create_task: WRITE: add a task to a project. POST /v1/workspaces/{workspaceId}/projects/{projectId}/tasks.
- clockify_create_client: WRITE: add a client to a workspace. POST /v1/workspaces/{workspaceId}/clients.
- clockify_create_tag: WRITE: add a tag to a workspace. POST /v1/workspaces/{workspaceId}/tags.

Screening checks:
- MCP handshake: pass (Answered in 259ms)
- Domain against threat feeds (Cloudflare security DNS): pass (clockify.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (21 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)