Clockify MCP server

What the model can do

Clockify time tracking: workspaces, projects with client, clients, workspace members, a person's time entries for a period with totals by project, time-off policies and requests, and timesheet approval requests; can also log time, start or stop a timer, change or delete a time entry, create or change projects, tasks and clients, add a tag, request time off, approve or reject time off and timesheets, and submit a timesheet, when you ask.

Reads

• clockify_workspacesThe Clockify workspaces this key can see, with their ids.
• clockify_projectsProjects in a Clockify workspace with client, billable flag and note (rates are not shown: their unit was not confirmed).
• clockify_clientsClients in a Clockify workspace.
• clockify_usersMembers of a Clockify workspace: name, email and status.
• clockify_time_entriesOne person's Clockify time entries for a period, newest first, with hours, description, project id, billable flag and totals by project.
• clockify_time_off_policiesTime-off policies in a Clockify workspace (id, name, whether requests need approval, half days, unit).
• clockify_time_off_requestsTime-off requests in a Clockify workspace for a period: who, which policy, dates and status (notes are not shown).
• clockify_approval_requestsTimesheet and expense approval requests in a Clockify workspace: who, which period, and state.

Acts, when you ask

These change something in Clockify. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• clockify_create_time_entryLog a completed time entry in Clockify for the connected user: when it started, how long it ran, what it was for, and optionally the project, task…
• clockify_create_clientAdd a client to a Clockify workspace, with an optional note.
• clockify_create_taskAdd a task to a Clockify project, with an optional estimate.
• clockify_create_tagAdd a tag to a Clockify workspace.
• clockify_start_timerStart a running Clockify timer for the connected user (a time entry with a start and no end), optionally on a project, task and tags.
• clockify_stop_timerStop the running Clockify timer of the connected user (or, with user_id and admin rights, of another member), ending it now or at the time given.
• clockify_update_time_entryChange an existing Clockify time entry (from clockify_time_entries): its start, end or length, description, project, task, tags or billable flag.
• clockify_delete_time_entryPermanently delete a Clockify time entry (from clockify_time_entries).
• clockify_create_projectCreate a project in a Clockify workspace, with an optional client, note, colour, billable flag and public flag.
• clockify_update_projectChange a Clockify project: rename it, archive or unarchive it, move it to another client, or change its note, colour, billable or public flag.
• clockify_update_taskChange a task on a Clockify project: rename it, mark it DONE or ACTIVE, change its estimate or billable flag, or set who is assigned…
• clockify_update_clientChange a Clockify client: rename it, archive or unarchive it, or change its note.
• clockify_create_time_off_requestRequest time off for the connected user under a Clockify time-off policy (from clockify_time_off_policies)…
• clockify_review_time_off_requestApprove or reject a pending Clockify time-off request (from clockify_time_off_requests), with an optional note.
• clockify_submit_timesheetSubmit the connected user's Clockify timesheet for a period for approval.
• clockify_review_approval_requestApprove or reject a submitted Clockify timesheet or expense approval request (from clockify_approval_requests)…

Connect it

First connect Clockify on Dashboard → Connections, then add Memtro to your client once. The Clockify tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Clockify connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › How many hours did I log on the Acme project this week?
• › What did Priya Nair log last week, by project?
• › Which projects belong to Brightwave Ltd, and are they billable?
• › Log two hours yesterday afternoon on the Northwind project for the data migration review
• › Start a timer on the BigCo onboarding project

Questions

Is this an official Clockify MCP server?

No. It is Memtro's MCP server with Memtro's Clockify connector behind it: the connector reads Clockify through its API with the credentials you connect on Dashboard → Connections, and Clockify publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Clockify?

Only when you ask, and only what it has been granted: log a completed time entry in a Clockify workspace; add a client to a Clockify workspace; add a task to a Clockify project; add a tag to a Clockify workspace; start a running Clockify timer as the connected user; stop a running Clockify timer; change a Clockify time entry; permanently delete a Clockify time entry; create a Clockify project; rename, archive or change a Clockify project; rename a Clockify task, mark it done, or change its estimate or assignees; rename, archive or change the note of a Clockify client; request time off under a Clockify time-off policy; approve or reject a Clockify time-off request; submit a Clockify timesheet for approval; approve, reject or withdraw a Clockify timesheet approval request. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server