Clockify time-tracking MCP: tools across 18 domains, read-only by default with opt-in writes.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like Clockify Time Tracking.
uvx clockify-mcp{
"CLOCKIFY_API_KEY": "YOUR_SECRET_VALUE",
"CLOCKIFY_ACCESS_MODE": "read",
"CLOCKIFY_DEFAULT_WORKSPACE_ID": "YOUR_VALUE_HERE"
}Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-tracegazer-clockify-mcp": {
"command": "uvx",
"args": [
"clockify-mcp"
],
"env": {
"CLOCKIFY_API_KEY": "YOUR_SECRET_VALUE",
"CLOCKIFY_ACCESS_MODE": "read",
"CLOCKIFY_DEFAULT_WORKSPACE_ID": "YOUR_VALUE_HERE"
}
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Clockify Time Tracking is an MCP server for Clockify time-tracking MCP: tools across 18 domains, read-only by default with opt-in writes.. It supports STDIO transport.
Use the generated config in Install. This server runs with uvx clockify-mcp; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for uvx clockify-mcp. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for uvx clockify-mcp. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for uvx clockify-mcp. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for uvx clockify-mcp. Add required environment variables before starting Cursor or VS Code.
Clockify Time Tracking uses STDIO transport. Use the package or command config in Install.
Clockify Time Tracking inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
Clockify Time Tracking is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
clockify-mcpstdio | pypi | 0.3.2 | Env: CLOCKIFY_API_KEY required secret Env: CLOCKIFY_ACCESS_MODE Env: CLOCKIFY_DEFAULT_WORKSPACE_ID |
ghcr.io/tracegazer/clockify-mcp:0.3.2stdio | oci | Not captured | Env: CLOCKIFY_API_KEY required secret Env: CLOCKIFY_ACCESS_MODE Env: CLOCKIFY_DEFAULT_WORKSPACE_ID |