Time Tracking
Clockify MCP connector
The Clockify connector brings clients, expenses, timesheet approval requests, cost rates and workspace settings into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can look up and update them inside their own Clockify access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Clockify to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Clockify once
-
Open Connections, choose Add connection, and pick Clockify.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Clockify API key. One person generates a token in Clockify and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Clockify MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Clockify MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Clockify MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Clockify to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Clockify through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Finance
Review expenses before the month closes
Ask for every expense logged in a Clockify workspace this month, grouped by client, and add the ones that came in by email without opening Clockify.
-
Finance
Update cost rates for the whole team
When salaries change, apply new cost rates across a Clockify workspace in one pass instead of editing each person by hand.
-
Operations
Keep the client list current
Add a new client to Clockify the moment a contract is signed, rename one after a rebrand, or archive one the work has ended for.
-
People
Chase approvals that are still waiting
List the timesheet approval requests still open in Clockify, see who submitted them, and approve or send back the ones that need a change.
-
Project management
Set up a workspace for a new engagement
Create a Clockify workspace, add the custom fields the client wants on every entry, and check which users already have access.
-
Agency leadership
Answer a client question from live records
When a client asks what was spent last week, pull the matching Clockify expenses and approval requests and summarize them in the reply.
Try asking
- “Which approval requests are still waiting in the Design workspace?”
- “List every expense logged for Acme this month.”
- “Add Northwind as a client in the Consulting workspace.”
AI tools
Clockify tools for your AI agents
169 tools are ready to call through Elaichi's MCP endpoint the moment you connect Clockify, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Clockify gets you
6 screens from the product, each doing one job for your Clockify account.
The agent
Ask about Clockify in plain language.
Get answers from live clients, expenses and approval requests, not a stale export.
- clients
- expenses
- approval requests
- workspaces
Ask Elaichi to work across your apps.
Which approval requests are still waiting in the Design workspace?
List every expense logged for Acme this month.
Add Northwind as a client in the Consulting workspace.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Use Clockify from Claude, ChatGPT or Cursor.
One governed endpoint for the whole organization, no SDK and no shared API key.
Copy the endpoint
Tool catalog
169 Clockify tools, ready without writing code.
Clients, expenses, approval requests, users, workspaces and custom fields covered end to end.
- Create a Clockify file image
- List all Clockify users
- List all Clockify workspaces
- Create a Clockify workspace
Toolboxes
Every team gets its own Clockify toolbox.
Finance sees expenses and cost rates, People sees approvals, each scoped separately.
- Finance
- People
- Operations
- Project management
Shared connections
Teammates work in Clockify without seeing keys.
One person connects, shares with teams and members, and the API key stays hidden.
- Finance
- People ops
- Consulting
- Agency EMEA
Audit log
Know who changed every Clockify record.
Each call is logged with who, when, what happened and which client or expense.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule runs the Clockify approval digest.
Open approval requests are fetched, grouped, drafted, approved by a person, then posted back.
Clockify digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch clients
Clockify
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Clockify
Queued
Collections and dashboards
Clockify health, computed without asking anyone.
Four metrics, 14 days of expenses created and a breakdown by team, refreshed on schedule.
Clockify health
Refreshed 4 minutes ago · every 15 minutes · from the clients collection
Clients
1,284 ↓ 12%
Expenses
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Clients created
Last 14 days
By team
Share of activity
Finance 34%
People ops 27%
Consulting 21%
Agency EMEA 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Clockify to Claude?
Connect Clockify in Elaichi first. Clockify signs in with an API key that you copy from your Clockify profile and paste into Elaichi, and there is no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Clockify clients, expenses and approval requests are available.
Does Clockify work with ChatGPT and Cursor as well as Claude?
Yes. Once Clockify is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Clockify once and every client uses it.
What can an AI agent actually do with my Clockify data?
It can list the clients, expenses, approval requests, users and workspaces in Clockify, look one up by name, and create or update them for you. In practice that means asking which approval requests are still waiting, adding an expense for a client, or setting new cost rates across a workspace. Short, concrete asks such as "add Northwind as a client" work better than long paragraphs.
Does connecting Clockify give the AI access to every workspace?
No. Every call to Clockify runs as the person who signed in, so the AI sees only the workspaces, clients and expenses that person can already see in Clockify. Elaichi can narrow that further with restrictions, and it can never widen it beyond what Clockify itself allows that person.
Can I stop an agent from deleting or changing things in Clockify?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Clockify clients and expenses while blocking deleting a client or changing cost rates. A restricted action is never shown to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
What happens to a Clockify connection when someone leaves?
Offboarding a person in Elaichi ends their access to Clockify through every client at once. If they connected Clockify and shared it, the shared connection keeps working for everyone else on the team. Disconnecting Clockify once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Clockify MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Clockify is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Put Clockify in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.