Enterprise DNA
M MCP Servers Developer low

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

T

MCP

tracegazer/clockify-mcp

Added 11 June 2026

#ai #claude #clockify #mcp #mcp-server #model-context-protocol #productivity #time-tracking

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

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