Clockify MCP Server
Enables time tracking integration with Clockify, including starting and stopping timers, managing projects and tasks, and summarizing time entries.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Clockify MCP Serverstart timer for project 'website' with description 'fixing navbar'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Unofficial agent plugin for Clockify: MCP tools plus Agent Skills — start/stop timers, enter time, and summarize sessions in Cursor and other MCP hosts.
Not affiliated with, endorsed by, or sponsored by Clockify or Cake.com. Third-party connector only.
Features
Feature | Description | Documentation |
Easy Installation | Single user-scoped MCP server utilizing a single Clockify API key | |
Granular Repo Integration | Initialize and configure on a per-repo basis | |
Easy Uninstallation | Skills and scripts rollback changes with guards to prevent overreach or harm | |
Good Hygiene | Plugin artifacts are gitignored by default | |
Three Time Entry Methods | Running timer, explicit start/stop times, automated using workflow triggers | |
IDE Layouts | Supports: single-window, multi-window, multi-root code workspace | |
Customize Time Entry | Configure nearest/up/down rounding, start/stop, increment, minimums, include seconds | |
Overlap guards | Handle overlapping time entries based on config | |
Config shapes | Repo as project (default) or repo as task — how git lines up with Clockify | |
Description templates | Use tokenized string with github properties or have the agent prompt you | |
Timer Runaway Prevention | Stop a timer after inactivity to prevent timer runaway |
Related MCP server: timely-mcp-server
How it works
Two modes. Both use the same Clockify project for a given repo config. Clockify still allows only one running timer. How that project maps to git (repo as project vs repo as task): Config: shape.
Mode | How time gets in | Skills |
Manual | You (or the agent, when you ask) start/stop a timer or log a completed range |
|
Automated | Agent follows Cursor rules/hooks from |
|
Getting started
Prerequisites
Need | Why |
Node 18+ (npm / npx) | Install script and the MCP |
Cursor (or AI Agent/IDE) | Run skills and MCP |
Clockify API key | MCP sevrver connection to Clockify |
If Cursor cannot find node / npx, see troubleshoot.
Additional Prerequisites
Install the plugin (once per machine)
Create a Clockify API key (Preferences → Advanced → Manage API Keys).
Run
npx -y -p @dustinestes/clockify-agent-plugin clockify-install-cursor— installs skills + global MCP (docs/install-cursor.md). Optional: Directory MCP button (MCP only; caveats).Reload Cursor; confirm Customize → MCP shows clockify-agent-plugin enabled.
Optional: pre-allow Clockify MCP tools so agents do not stall on an Allow / Always allow prompt mid-run.
Credentials, allowlists, and non-Cursor hosts: docs/use.md.
Add Clockify to a repo (each repo)
In that repo, run
/clockify-init— choose Clockify workspace, write config, ignore, Clockify project, optional GitHub label→task sync. After this you can enter time with skills (start/stop timer, enter-time, summarize).Optional: run
/clockify-automateso the agent starts/stops timers fromautomated.triggers(issues/PRs).
To undo a repo without uninstalling the plugin: docs/use.md.
Skills
You talk to the agent in plain language (or run a /skill). The agent calls MCP tools; you do not.
Setup skills (
init,uninit,automate,unautomate) are slash-only so they do not fire by accident.
Group | Skill | Purpose | Example |
Repo | Setup the current working directory (config + ignore + project + GitHub label→task sync) |
| |
Repo | Full local teardown (keep plugin unless asked) |
| |
Mode | Agent mode on: Cursor rules/hooks from |
| |
Mode | Agent mode off: remove rule/hooks; keep |
| |
Timer | Start a running timer ( |
| |
Timer | Stop the running timer |
| |
Timer | Read-only running timer (or none) |
| |
Time | Completed range, no rounding ( |
| |
Review | Today / range totals |
|
Developing
Working on this repo: docs/develop.md. Shipping a release or Directory listing: docs/publish.md. How to contribute: CONTRIBUTING.md.
Clockify Agent Plugin
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceMCP Server to log time and view Jira statistics directly from Cursor IDE.
- FlicenseNot gradedqualityBmaintenanceMCP server for Timely time tracking API. Connects Claude Code to your Timely account for reading and creating time entries, projects, tasks, and users.4
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to interact with Clockify time tracking via curated workflows and a generic API tool for managing workspaces, projects, tasks, and time entries.8MIT
- AlicenseBqualityCmaintenanceMCP server for Clockify time tracking, enabling CRUD operations on workspaces, projects, tasks, clients, tags, users, and time entries.36MIT
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for generating rough-draft project plans from natural-language prompts.
MCP server for interacting with the Supabase platform
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dustinestes/clockify-agent-plugin'
If you have feedback or need assistance with the MCP directory API, please join our Discord server