A
licenseA
qualityB
maintenanceMCP server for Kimai time-tracking that provides read access to the full API and guarded write tools for timesheets, with explicit authorization and backups.
28
22 npm
AGPL 3.0
kimai-task-tracker-mcp
Related Servers
Alternatives to kimai-task-tracker-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceThis MCP server enables AI assistants to interact with the Timing application for managing time tracking and tasks, including project and time entry operations.7MIT
- AlicenseAqualityCmaintenanceEnables MCP-capable clients to read and write Kimai timesheets using a personal API token, supporting natural language time logging, timers, and timesheet management.15MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for managing Kaiten tasks through AI agents like Claude, enabling task retrieval, creation, updating, and time logging.14 npm2MIT
- AlicenseBqualityBmaintenanceAn MCP server for logging time entries locally and synchronizing them with OpenProject, enabling natural language time tracking and upload to OpenProject.1612 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server for Productive.io that enables users to log time, inspect projects, and manage time entries using natural language commands. It features fuzzy project matching, local caching, and remembers default services per project for streamlined time tracking.14MIT
TDQS
A4/5.0
Scored across 10 tools
Disambiguation5/5
Each tool targets a distinct operation: timer control (start_task, stop_timesheet), manual logging (log_time), time queries (get_task_time, get_project_summary), task management (list_tasks, create_task, mark_task_done, reopen_task), and tag listing (list_tags). Even similar actions like start_task and log_time are clearly separated by explicit vs. timer-based logging.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., start_task, get_project_summary, mark_task_done). No mixed conventions or vague verbs; the naming is predictable and readable.
Tool Count5/5
With 10 tools, the set is well-scoped for a task tracker with time tracking. Each tool serves a clear purpose and covers the essential operations without redundancy or bloat.
Completeness4/5
The toolset covers the core lifecycle: task creation, listing, status updates (done/reopen), and comprehensive time tracking (start, stop, manual log, queries, project summary). Minor gaps exist, such as no update/delete task or tag assignment, but these are not critical for the primary workflow.
Maintenance
ActivitySlowing
ResponsivenessNo issues