tracegazer/clockify-mcp
by Various
Full-coverage Clockify MCP — 112 tools across 18 domains (incl. invoices, scheduling, time-off & approvals), native OpenTelemetry observability, and a 3-tier read/time-tracking/ful
MCP
tracegazer/clockify-mcp
Added 11 June 2026
Overview
A Python-based MCP server that exposes 112 tools across 18 Clockify domains including invoices, scheduling, time-off, and approvals. It includes native OpenTelemetry observability and uses a three-tier access model for read, time-tracking, and full access.
Best for
Best for
Developers building AI assistants that need comprehensive Clockify integration
Use cases
- Automating Clockify time entries and updates via AI agents
- Querying Clockify reports and scheduling data through a model context protocol
- Managing approvals and invoices with an AI assistant
How to use
Install
uvx clockify-mcp Tools exposed
time-trackingCLOCKIFY_API_KEYCLOCKIFY_REGIONCLOCKIFY_BASE_URLCLOCKIFY_DEFAULT_WORKSPACE_IDCLOCKIFY_ACCESS_MODECLOCKIFY_ENABLE_WRITESCLOCKIFY_TELEMETRYCLOCKIFY_TELEMETRY_DETAIL
Tested with
Claude Desktop
Notes
A Python-based MCP server that exposes 112 tools across 18 Clockify domains including invoices, scheduling, time-off, and approvals. It includes native OpenTelemetry observability and uses a three-tier access model for read, time-tracking, and full access.
0 stars on GitHub. Last updated 2026-06-09. Licensed MIT.
Use cases
- Automating Clockify time entries and updates via AI agents
- Querying Clockify reports and scheduling data through a model context protocol
- Managing approvals and invoices with an AI assistant
Pros
- Covers nearly all Clockify domains with 112 tools for comprehensive integration
- Built-in OpenTelemetry observability enables monitoring and debugging
- Three-tier access model provides granular permission control
Cons
- Requires a compatible MCP host environment to run
- Large tool surface may be excessive for simple time-tracking needs
- Performance depends on Clockify API availability and rate limits
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Covers nearly all Clockify domains with 112 tools for comprehensive integration
- Built-in OpenTelemetry observability enables monitoring and debugging
- Three-tier access model provides granular permission control
Cons
- Requires a compatible MCP host environment to run
- Large tool surface may be excessive for simple time-tracking needs
- Performance depends on Clockify API availability and rate limits
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.
