A
licenseA
qualityC
maintenanceEnables interaction with the Clockodo time tracking API, providing tools, prompts, and resources for time tracking, HR analytics, and team management with role-based access.
16
3
MIT
mcp-clockodo
by kenzotp
Related Servers
Alternatives to mcp-clockodo
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables logging, listing, updating, deleting, and summarizing timesheet entries, starting and stopping timers, checking timer status, and exporting time data through natural language, backed by a local SQLite database.6 npmMIT
- AlicenseAqualityDmaintenanceEnables time tracking and management in Clockify through natural language commands. Supports creating time entries, managing projects, clients, and tags.1325 npmMIT
- AlicenseAqualityCmaintenanceEnables viewing, creating, and managing time registrations, absences, and timesheet approvals through the Timelog API using natural language.211ISC
- AlicenseNot gradedqualityAmaintenanceEnables LLMs to log and manage time entries, control timers, review unbilled hours, and prepare draft Moneybird invoices through natural language.1MIT
- AlicenseNot gradedqualityCmaintenanceIntegrates with Clockify to manage time entries through natural language prompts, allowing users to register and track their work time directly via LLM conversations.27MIT
TDQS
A3.7/5.0
Scored across 13 tools
Disambiguation4/5
Each tool targets a distinct resource or action: me/entries/customers/projects/users/texts/clock are clearly separated. The only slight ambiguity is between clockodo_clock_delete (stopping/discarding a running clock) and clockodo_delete_entry (deactivating a saved entry), but descriptions clarify the difference.
Naming Consistency3/5
Most entry-related tools follow a clean verb_noun pattern (list_entries, get_entry, create_entry, update_entry, delete_entry), but the clock tools use noun_verb (clock_start, clock_delete, clock_status) and clockodo_me breaks the pattern entirely. This mixed convention is readable but inconsistent.
Tool Count5/5
13 tools cover the essential Clockodo surface without bloat: authentication, entry CRUD, supporting list lookups, and live clock management. Each tool has a distinct purpose and the count feels appropriate for a time-tracking MCP server.
Completeness3/5
The server covers entry CRUD, listing of customers/projects/users/texts, and clock start/status/discard, so core workflows are present. However, create_entry requires services_id and there is no list_services tool, forcing agents to guess an ID. This is a notable gap that will cause failures when creating entries.
Maintenance
ActivityMaintained
ResponsivenessNo issues