MCP.Market

Task tracking (sessions, ETA, dashboard) MCP server

by amineutron·io.github.amineutron/mcp-tracking·v0.3.0
No reviews yet

Track long-running tasks in real time: sessions, steps, speed, ETA, HTTP API and TUI dashboard.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

not scanned yet

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Task tracking (sessions, ETA, dashboard) yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Task tracking (sessions, ETA, dashboard) tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Task tracking (sessions, ETA, dashboard) compares

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 90% of 1,297 Productivity servers

Release history: 2 versions in the registry since 2026-09-24, latest 2026-10-31, typically one every 38 days.

Install Task tracking (sessions, ETA, dashboard) in Claude Code, Cursor or VS Code

claude mcp add mcp-tracking -- uvx mcp-tracking
Add to Cursor

What the publisher says

From the Task tracking (sessions, ETA, dashboard) repository's README, as published. We do not edit it. Read it on GitHub

MCP Tracking

<!-- mcp-name: io.github.amineutron/mcp-tracking -->

English summary. Local-first tracking of long-running tasks: an MCP server for Claude or Lyra, a small HTTP API on 127.0.0.1:8765 and a Textual terminal dashboard. Sessions have items, progress, logs and templates (download, machine, free, lyra_task, movie); pollers feed qBittorrent and Bazarr sessions automatically. Install: pip install . then mcp-tracking, mcp-tracking-api, mcp-tracking-ui. No cloud, no telemetry.

Serveur MCP de suivi en temps reel avec dashboard terminal. Permet a Claude/Lyra de tracker n'importe quelle operation longue ET alimente automatiquement les sessions depuis le media-server (qBittorrent, Bazarr, conversion DV).

Demo

Enregistree avec docs/demo/record.sh : server.py --test alimente quatre sessions simulees dans un repertoire d'etat temporaire (TRACKINGSTATEDIR), puis server.py --ui ouvre le dashboard dessus. Les sessions reelles ne sont pas touchees.

Sommaire

  • Architecture
  • Installation
  • Services systemd
  • Lancement
  • Dashboard
  • Integration media-server
  • Outils MCP
  • Templates
  • Securite
  • Ajouter un template

Architecture

MCP/tracking/
  server.py              -- Serveur MCP (outils Claude/Lyra) + point d'entree --ui / --test
  api.py                 -- API HTTP locale (127.0.0.1:8765) pour les scripts externes
  mutations.py           -- Mutations d'une session, partagees par api.py ET server.py
                            (horodatage items, historique, niveaux de log, auto-completion)
  metrics.py             -- Metriques derivees (vitesse, ETA, ecoule, stale) -- logique pure,
                            calculees a la lecture, jamais stockees
  storage.py             -- Persistence JSON atomique + verrou fichier + cache mtime + purge TTL
  models.py              -- Modeles pydantic (TrackingSession, TrackingItem, LogEntry, ProgressPoint)
  templates.py           -- Templates builtin + templates utilisateur (JSON)
  ui.py                  -- Dashboard Textual (TUI temps reel) + modales stop/kill
  sim.py                 -- Simulations de demo (server.py --test)
  poller.py              -- Daemon polling qBittorrent (10s) + Bazarr (60s)
  tracking-api.service   -- Unite systemd (systeme) pour api.py
  tracking-poller.service -- Unite systemd (systeme) pour poller.py
  install.sh / deploy.sh -- Inst

Fichiers d'etat et configuration

Un ancien tracking_state.json a cote du code est migre automatiquement au premier demarrage (copie, jamais supprime).

Variables d'environnement de retention :

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Task tracking (sessions, ETA, dashboard): common questions

Is Task tracking (sessions, ETA, dashboard) MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Task tracking (sessions, ETA, dashboard) safety report
How do I install Task tracking (sessions, ETA, dashboard)?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Task tracking (sessions, ETA, dashboard) need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is Task tracking (sessions, ETA, dashboard) maintained?
The last commit was 39 days ago (2026-09-24). The latest release is v0.3.0.
What can I use instead of Task tracking (sessions, ETA, dashboard)?
Servers from other publishers that do the same job: loci MCP server, INSSIST MCP server and Enquire MCP server.

Alternatives to Task tracking (sessions, ETA, dashboard)

Same job from other publishers: the closest match first, then the best rated.

  • loci
    Cross-session memory and hybrid RAG over your notes and docs. Local-first, with cited answers.
    A
  • INSSIST
    Drive your own logged-in Instagram session via the INSSIST extension: read, publish, DMs, analytics.
    A
  • Enquire
    Long-term memory for AI agents — your Obsidian vault as searchable persistent memory.
    A

More from amineutron →