drytrix-timetracker-mcp

A Model Context Protocol (MCP) server for DRYTRIX/TimeTracker — the self-hosted, open-source time-tracking app. It exposes your tracked hours, projects, and reports as MCP tools over TimeTracker's stable /api/v1 REST API, so any MCP client (OpenCode, Claude Desktop, …) can query your time data in natural language.

It is configured entirely through environment variables; nothing is baked in.

Requirements

• Python 3.11+

• A running TimeTracker instance (tested on v5.13.4; targets v5.13+)

• An API token created in TimeTracker under Admin → Security & Access → Api-tokens

Recommended token scopes

read:time_entries, read:projects, read:reports, read:clients, read:tasks — or simply read:* to grant all read access in one checkbox.

whoami and per-user scoping need read:users. On instances that do not list that scope, read:* covers it — the app treats read:* as matching any read:<resource>. Add write:time_entries only if you enable the write tools. Missing scopes degrade gracefully: a tool that lacks its scope returns a clear 403 naming the scope.

Related MCP server: Clockify Time Tracking

Install & run

uvx drytrix-timetracker-mcp

or install it:

uv tool install drytrix-timetracker-mcp

Configuration

Environment variables (a local .env in the working directory is also read):

MCP client config

{
  "mcpServers": {
    "timetracker": {
      "command": "uvx",
      "args": ["drytrix-timetracker-mcp"],
      "env": {
        "TT_BASE_URL": "https://time.example.com",
        "TIMETRACKER_API_KEY": "tt_your_token_here"
      }
    }
  }
}

Tools

Read (always available)

Write (only when TT_ENABLE_WRITE=true, scope write:time_entries)

start_timer, stop_timer, pause_timer, resume_timer, create_time_entry

Notes

• hours_by_day is preferred over get_hours_summary. TimeTracker's /reports/summary treats a date-only end_date as midnight and silently drops the final day; this server normalizes ranges and computes hours_by_day directly from time entries, so the two can disagree. hours_by_day is right.

• Aggregates are scoped to the token's own user. Without the read:users scope the user cannot be resolved, and the result carries a note that it may span users.

• Endpoints that don't exist on your version return a clear error rather than a stack trace.

License

MIT