clockify-mcp
Related Servers
Alternatives to clockify-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceA scoped MCP server for managing Clockify workspaces, offering read/write tools for clients, projects, tasks, tags, and time entries, with idempotent structure scaffolding and gated deletion.-
- AlicenseBqualityBmaintenanceAn MCP server for Clockify that provides tools for managing timers, time entries, projects, tasks, tags, people, reports, and time off, with natural language parsing of times and durations.612MIT
- AlicenseBqualityDmaintenanceMCP 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.95 npmMIT
- FlicenseNot gradedqualityBmaintenanceA modular MCP server integrating Clockify, WakaTime, and Azure DevOps for time tracking, work item management, and time logging via a unified API.2-
- AlicenseNot gradedqualityAmaintenanceRead-only MCP server for Clockify time tracking, exposing 60 raw read tools and five workflows for status, workspace overview, and review of days/weeks.MIT
- MIT
TDQS
Scored across 36 tools
Each tool targets a distinct resource and action (e.g., add_client, delete_client, get_client, update_client), with no overlapping purposes. The resource type is always clear from the name.
All tool names follow a consistent verb_noun pattern using snake_case (add_, delete_, get_, update_). The few exceptions like get_current_user or get_reports_detailed still adhere to the pattern.
36 tools cover CRUD for multiple resources (clients, projects, tags, tasks, time entries, users) plus workspaces and reports. While on the higher end, it is appropriate for Clockify's API scope.
The tool set covers all major CRUD operations for each resource, plus specific queries like get_time_entries_for_project and report endpoints. No obvious gaps for typical usage.