Time Tracking
Clockify MCP connector
The Clockify connector brings clients, expenses, timesheet approval requests, cost rates and workspace settings into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can look up and update them inside their own Clockify access.
- Connects with an API key
- Free 14-day trial
- No credit card
Which approval requests are still waiting in the Design workspace?
Working in Clockify with Elaichi
-
List all Clockify users
-
List all Clockify workspaces
-
Get single Clockify workspace by ID
How to connect Clockify to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
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. 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.
Clockify MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Clockify through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Clockify is logged.
-
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.”
What connecting Clockify gets you
6 screens from Elaichi, each doing one job for your Clockify account.
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, Cursor or Microsoft Copilot
The agent
Ask about Clockify in plain language.
Get answers from live clients, expenses and approval requests, not a stale export.
Copy the endpoint
AI apps
Use Clockify from Claude, ChatGPT, Cursor or Microsoft Copilot.
One governed endpoint for the whole organization, no SDK and no shared API key.
Tool catalog
169 Clockify tools, ready without writing code.
Clients, expenses, approval requests, users, workspaces and custom fields covered end to end.
Toolboxes
Every team gets its own Clockify toolbox.
Finance sees expenses and cost rates, People sees approvals, each scoped separately.
Shared connections
Teammates work in Clockify without seeing keys.
One person connects, shares with teams and members, and the API key stays hidden.
Audit log
Know who changed every Clockify record.
Each call is logged with who, when, what happened and which client or expense.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Clockify digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Clockify
Queued
Workflows
A schedule runs the Clockify approval digest.
Open approval requests are fetched, grouped, drafted, approved by a person, then posted back.
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%
Collections and dashboards
Clockify health, computed without asking anyone.
Four metrics, 14 days of expenses created and a breakdown by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Clockify
All three can connect Clockify to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Clockify tools | Allow or restrict single Clockify tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Clockify call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting deleting a client or changing cost rates. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Clockify?
Yes. Both let Claude, ChatGPT or Cursor use Clockify. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Clockify call.
How is Elaichi different from Composio for Clockify?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Clockify: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Clockify in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot