Task Tracker

Provides an MCP server that integrates Linear task management with TrackingTime time tracking for task creation, status updates, and time tracking.
  • typescript

1

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "reminia-task-tracker": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/task-tracker",
        "run",
        "task-tracker"
      ]
    }
  }
}

You have a Task Tracker MCP Server that unifies Linear task management with TrackingTime time tracking. It lets you create and manage tasks, update statuses, start and stop time tracking, and attach notes, all through natural language workflows handled by an MCP client.

How to use

You interact with the Task Tracker MCP Server through an MCP client. Use it to create tasks, assign them to projects, set or update task statuses, view tasks by their state, search by title, and manage time tracking for work on tasks. You can start a timer when you begin work on a task, stop it when you pause, view the currently active tracking task, and add notes to the tracking entry. These actions are designed to streamline your daily flow and keep your task and time data in sync across Linear and TrackingTime.

How to install

Prerequisites: you need a runtime that supports the MCP server workflow and access to the required environment file. Ensure you have the necessary tooling installed to run the server as described here.

  1. Prepare environment variables by creating an environment file from the example if provided in your setup. Each variable should be defined according to your workspace and integration needs.

  2. Build or install dependencies and start the server using the provided commands. You can either run the build script or execute the runtime commands directly.

  3. If you are configuring the MCP client installer, use the exact command and arguments shown in the client integration snippet for your platform. The following is an example of the local startup command used to run the server locally via the MCP client configuration.

uv build 
uv run task-tracker
{
  "mcpServers": {
    "task-tracker": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/task-tracker",
        "run",
        "task-tracker"
      ]
    }
  }
}

Additional configuration

To run as an MCP server, you typically use the stdio configuration described above. This runs the server locally and expects the working directory to contain your task-tracker project. If you need to adjust where the server runs from, modify the --directory argument accordingly.

Available tools

Task creation

Create new tasks in Linear with optional project, description and state assignments.

Set and switch current working team

Set the active Linear team context for subsequent task operations.

Get projects

Retrieve a list of projects from Linear.

View tasks by status

Filter and view tasks categorized by backlog, unstarted, started, done, or canceled.

Search tasks by title

Find tasks by their title using a simple search query.

Update task status

Change the status of existing tasks in Linear.

Start time tracking

Begin a TrackingTime timer for a specific task.

Stop time tracking

Stop the currently active TrackingTime timer.

View active tracked task

Show the task currently being tracked in time.

Add notes to tracking task

Append notes to the active time-tracking entry.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational