@lewinnovation/clockify-mcp-server
MCP 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.
README
@lewinnovation/clockify-mcp-server
MCP (Model Context Protocol) server for the Clockify REST API. It exposes a small set of curated tools for common workflows plus a generic clockify_request tool for other documented /v1/... endpoints.
Requirements
- Node.js 20+
- pnpm 10+
- A Clockify API key (profile settings)
Install
# via npx
npx @lewinnovation/clockify-mcp-server
# OR via pnpm globally
pnpm add -g @lewinnovation/clockify-mcp-server
# OR clone and install locally
pnpm install
pnpm run build
Configuration
| Variable | Required | Description |
|---|---|---|
CLOCKIFY_API_KEY |
Yes | Sent as X-Api-Key on every request. |
CLOCKIFY_API_BASE_URL |
No | Defaults to https://api.clockify.me/api. Override only if Clockify documents a different base for your account or region. |
Run (stdio)
The server speaks MCP over stdio (stdout must stay clean JSON-RPC; logs go to stderr).
export CLOCKIFY_API_KEY="your-key"
pnpm start
Or after pnpm run build:
node dist/index.js
MCP tool handlers are registered from src/tools/register.ts (shared helpers in src/tools/helpers.ts).
MCP client setup (popular AI agent tools)
Use this server definition in your MCP client:
{
"mcpServers": {
"clockify": {
"command": "npx",
"args": ["-y", "@lewinnovation/clockify-mcp-server"],
"env": {
"CLOCKIFY_API_KEY": "your-key"
}
}
}
}
If you prefer running a local clone, use:
{
"mcpServers": {
"clockify": {
"command": "node",
"args": ["/absolute/path/to/clockify-mcp-server/dist/index.js"],
"env": {
"CLOCKIFY_API_KEY": "your-key"
}
}
}
}
Cursor
Add the JSON entry above to:
- Workspace config:
.cursor/mcp.json - Or user config:
~/.cursor/mcp.json
Then reload Cursor (or restart the MCP server from Cursor settings).
Claude Desktop
Add the same mcpServers.clockify entry to Claude Desktop MCP config:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
Restart Claude Desktop after saving the config.
Claude Code (CLI)
From your project directory:
claude mcp add clockify --env CLOCKIFY_API_KEY=your-key -- npx -y @lewinnovation/clockify-mcp-server
Or add the same JSON server entry to your Claude Code MCP config file if you manage MCP servers declaratively.
Other MCP-compatible agent tools
For tools such as Cline, Roo Code, and Windsurf, add the same server command/env block in that tool's MCP server settings UI or config file:
command:npxargs:["-y", "@lewinnovation/clockify-mcp-server"]env.CLOCKIFY_API_KEY: your Clockify API key
The server uses stdio transport, so no host/port configuration is required.
Tools
Curated
get_current_user—GET /v1/userlist_workspaces—GET /v1/workspaces(optional singlerolefilter; multiple roles requireclockify_request)list_projects—GET /v1/workspaces/{workspaceId}/projectswith pagination (page,page_size→page-size)list_tasks—GET /v1/workspaces/{workspaceId}/projects/{projectId}/taskslist_time_entries—GET /v1/workspaces/{workspaceId}/user/{userId}/time-entries(ifuser_idis omitted, the current API user is resolved viaGET /v1/user)create_time_entry—POST /v1/workspaces/{workspaceId}/time-entriesupdate_time_entry—PUT /v1/workspaces/{workspaceId}/time-entries/{id}(Clockify requiresstarton updates)stop_running_time_entry—PATCH /v1/workspaces/{workspaceId}/user/{userId}/time-entrieswith{ end }(optionaluser_id, default current user)
Generic
clockify_request—method,path(must start with/v1/), optionalquerymap, optional JSONbody(max 256 KiB serialized). Array query values are sent as repeated keys.
Responses wrap JSON in a text content block; when Clockify returns a Last-Page header, curated list-style tools include lastPage in the decoded JSON payload.
OpenAPI types
Types are generated from Clockify’s OpenAPI document:
pnpm run generate:openapi
Source URL: https://api.clockify.me/api/v3/api-docs
Output: src/generated/clockify.d.ts
Re-run this periodically to pick up API changes, then fix any compile errors from type drift.
Scripts
| Script | Purpose |
|---|---|
pnpm run dev |
Watch src/index.ts with tsx. |
pnpm run build |
Emit dist/ with tsc. |
pnpm run typecheck |
tsc --noEmit. |
pnpm run smoke |
Mocked HTTP smoke test for curated endpoints (no API key needed; uses a dummy key + mocked fetch). |
pnpm run generate:openapi |
Regenerate src/generated/clockify.d.ts. |
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.