This MCP server, task-tracker, bridges Linear for task management with TrackingTime for time tracking. It enables creating and updating tasks, viewing tasks by status, and starting/stopping time tracking directly through the MCP interface. With the integrated tools, you can create tasks with optional project and status assignments, fetch lists of projects, and search or filter tasks by title. Time-tracking capabilities let you start a timer for a task, stop an active timer, view the currently tracked task, and append notes to time entries. All actions are exposed through the MCP commands so you can automate workflows via natural language prompts or Claude Desktop/MCP clients.

Prerequisites:

• Python environment with the MCP toolchain (uv) installed
• Access tokens for Linear and TrackingTime APIs
• Git

Installation steps:

1. Clone the repository that contains the MCP server (task-tracker): git clone https://github.com/reminia/task-tracker.git cd task-tracker

2. Prepare environment variables.

   • Copy the example env file and fill in credentials: cp .env.example .env

     Edit .env to include:

     LINEAR_API_KEY=your_linear_api_key

     LINEAR_TEAM_ID=optional_default_team_id

     LINEAR_PROJECT_ID=optional_default_project_id

     TRACKINGTIME_API_KEY=your_trackingtime_api_key

     TRACKINGTIME_USER_ID=optional_user_id

3. Build the MCP server package (as required by the project setup): uv build

4. Run the MCP server locally: uv run task-tracker

5. Optional: configure in Claude Desktop or your MCP client using the provided mcpServers section, e.g.: { "mcpServers": { "task-tracker": { "command": "uv", "args": [ "--directory", "/path/to/task-tracker", "run", "task-tracker" ] } } }

Tips and common considerations:

• Ensure your Linear and TrackingTime API keys have the necessary permissions for reading projects, creating/updating tasks, and managing time entries.
• If using default IDs (TEAM_ID or PROJECT_ID), ensure they exist in your Linear workspace to avoid failures when creating tasks.
• The environment variables are documented in the .env example; keep sensitive keys secure and do not commit them to public repos.
• If you encounter connectivity issues, verify network access to Linear and TrackingTime APIs and confirm that the uv toolchain is properly installed and configured.
• You can customize task queries and time-tracking behavior via environment variables or MCP configuration where supported by the server implementation.
• The .env file path may be overridden by your deployment setup; ensure the MCP process can access the file.