Skip to main content
Glama
Tracker MCP Server
by egormak

Tracker MCP Server

This is an MCP (Model Context Protocol) server designed to connect to your local tracker-server. It exposes endpoints like checking and applying today's schedule, retrieving statistics, registering tasks, and managing timers directly to LLM clients (like Claude Desktop or Cursor).

Prerequisites

  • A running instance of tracker-server (usually on http://localhost:3000).

  • Python 3.11+ (if running locally) or Docker.


Related MCP server: mcp-server-tasktracker

When you deploy your MCP agent, you can hook it directly to the Docker image provided from the GitHub Container Registry.

Because tracker-server is running on your host machine locally, Docker needs to know how to reach it. The image defaults to http://host.docker.internal:3000 assuming you are on Mac/Windows or using Docker Desktop.

For Claude Desktop configuration (claude_desktop_config.json):

{
  "mcpServers": {
    "tracker-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "TRACKER_API_URL=http://host.docker.internal:3000",
        "ghcr.io/egormak/tracker-mcp:latest"
      ]
    }
  }
}

CI publishes latest, a date tag (YYYY-MM-DD), an hour tag (YYYY-MM-DD-HH, UTC) and a short-sha tag (sha-xxxxxxx) on every push to main (a manual run from another branch publishes only the sha tag); pin one of the latter for reproducible setups.

If your tracker-server requires authentication, also pass -e TRACKER_API_KEY=<token> (sent as the X-Bot-Token header).

Note: Notice the -i flag. Because MCP communicates over stdin/stdout (stdio), you must run the docker container interactively, but without a TTY (-t).


๐Ÿ›  Running Locally

If you are developing or simply prefer to run from source instead of Docker.

  1. Setup the Virtual Environment:

    cd tracker-mcp
    python -m venv venv
    source venv/bin/activate
    pip install -r requirements.txt

    Run the test suite (no live tracker-server needed):

    pip install -r requirements-dev.txt   # adds pytest and pytest-asyncio
    pytest
  2. Run the MCP Server manually:

    # Make sure your tracker server is running!
    python server.py

    Note: This will just block your terminal waiting for stdio MCP JSON RPC commands. This is expected.

  3. Configure Claude Desktop (Local Mode):

    {
      "mcpServers": {
        "tracker-mcp": {
          "command": "/absolute/path/to/tracker-mcp/venv/bin/python",
          "args": [
            "/absolute/path/to/tracker-mcp/server.py"
          ],
          "env": {
            "TRACKER_API_URL": "http://localhost:3000"
          }
        }
      }
    }

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelogโ€ฆ

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables LLM clients to manage tasks, timers, and notes in Rhizm through natural language commands. It provides tools for task operations, time tracking, and note management via API integration.
      11
      6 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that lets LLMs interact with your Clockify workspace for time-tracking automation and reporting, enabling natural language logging of time entries, querying entries, and generating reports.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients to query a self-hosted TimeTracker instance over its /api/v1 REST API, exposing tracked hours, per-day and per-project summaries, projects, clients, tasks, search, and active-timer status in natural language. Optionally registers write tools to start, stop, pause, resume, and create timers or time entries when write mode is enabled.
      10
      MIT