A
licenseA
qualityC
maintenanceEnables MCP-capable clients to read and write Kimai timesheets using a personal API token, supporting natural language time logging, timers, and timesheet management.
15
MIT
drytrix-timetracker-mcp
Officialby fzl-jeroen
Related Servers
Alternatives to drytrix-timetracker-mcp
No user-submitted related servers found.
Related Servers
Timesheet MCP Serverofficial
AlicenseBqualityBmaintenanceEnables natural language control of the Timesheet API for timer management, task tracking, and project management through MCP tools.5047 npm1MIT- AlicenseNot gradedqualityCmaintenanceEnables natural language time tracking and booking for WorkTracker via MCP tools, allowing users to assign time, list projects, and manage daily schedules through conversational commands.MIT
- FlicenseNot gradedqualityCmaintenanceExposes the full public TSheets REST API v1 as MCP tools, enabling time tracking, scheduling, and PTO management operations via natural language.-
- AlicenseCqualityCmaintenanceEnables interacting with Clockify time-tracking data through natural language, providing tools to manage workspaces, projects, time entries, reports, and more via the MCP protocol.4832 PyPI1MIT
- 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.7 npmMIT
TDQS
B3.1/5.0
Scored across 10 tools
Disambiguation4/5
Most tools target clearly distinct resources: clients, projects, tasks, users, timer status, and API metadata. The one genuine overlap is get_hours_summary vs hours_by_day, both reporting hours, though the descriptions clarify that one is a billable/total rollup and the other is the authoritative per-day source. search also lightly overlaps with the list_* tools but is framed as a cross-entity search.
Naming Consistency3/5
Five tools follow a clean list_noun pattern (list_projects, list_clients, list_tasks, list_time_entries), but the rest deviate: bare nouns (whoami, api_info, timer_status), a bare verb (search), a get_ prefix (get_hours_summary), and a noun_phrase (hours_by_day). The names are individually readable but there is no single predictable convention an agent can rely on.
Tool Count5/5
Ten tools is well within the sweet spot for a time-tracking server, and each covers a distinct slice of the domain (metadata, identity, projects, clients, tasks, entries, summaries, timer, search). Nothing feels padded or redundant in count.
Completeness2/5
The surface is entirely read-only: there is no way to start/stop a timer, log or edit a time entry, or create projects/tasks/clients, even though timer_status implies an active-timer lifecycle exists. For a time tracker, the inability to record time is a significant gap that will block common agent workflows.
Maintenance
ActivityMaintained
ResponsivenessNo issues