A
licenseNot graded
qualityD
maintenanceModel Context Protocol server for the mite time tracking API, enabling time entries, stopwatch, customers, projects, and services management through natural language.
6 npm
1
MIT
mite
by Stefan39
Related Servers
Alternatives to mite
No user-submitted related servers found.
Related Servers
DuTemps MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables coding agents such as Claude Code or Codex to run and stop the timer, log, correct, delete and restore time entries, read settings, projects, clients, tags, entries and reports, and preview invoices or create and edit invoice drafts. It communicates over stdin/stdout without opening a port, writes to the same audited database as the app, and leaves issuing or voiding invoices to the user in the app.MIT- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with KIMAI 2 time tracking for managing timesheets, projects, activities, customers, and generating reports.MIT
- AlicenseAqualityBmaintenanceEnables querying and managing Clockodo time-tracking data through natural language, with read tools for daily use and guarded write tools for safe edits.13MIT
- 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
- AlicenseAqualityBmaintenanceA read-only MCP server for querying Timely time tracking data, providing tools for project overviews, time spent summaries, and work log entries.3MIT
TDQS
A4.2/5.0
Scored across 12 tools
Disambiguation4/5
Most tools target distinct operations; the main ambiguity is among the four report tools, but descriptions explicitly route between them (fixed project-by-month, flexible grouping, budget, billable ratio). `mite_list_projects` also exposes budget fields while `mite_report_budget` handles budget usage, but the boundary is stated.
Naming Consistency4/5
Names use a consistent `mite_` prefix and snake_case, mostly following a verb_noun pattern such as `list_time_entries`, `get_time_entry`, and `report_budget`. Minor deviations are `whoami`, bare `report`, and `tracker_status`, but they remain readable and predictable.
Tool Count5/5
Twelve tools is well within the ideal range and each supports a clear part of the read/report workflow: identity, reference lists, time entries, tracker status, and aggregations. No obvious redundant filler.
Completeness3/5
The surface covers read-only lookups and reporting well, including time entries, reference data, budgets, and billable ratios. However, there are no create/update/delete operations for time entries and no start/stop tracker controls, so lifecycle coverage is notably incomplete if the server is meant to support time tracking rather than only reporting.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive