tracking
Related Servers
Alternatives to tracking
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to open and update session work, report goals, tasks, blockers, outcomes, and subagent contributions, and resume compact context after interruptions. A local dashboard then visualizes multiple sessions and live updates without requiring additional model calls.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to launch, monitor, and manage background shell jobs with durable event tracking, live progress dashboards, and wake-on-attention for interactive sessions.1Apache 2.0
- AlicenseBqualityCmaintenanceEnables AI agents to start, monitor, follow up on, stop, and collect results from headless Claude Code CLI sessions, with queuing, budgets, locks, and wake-up notifications.9MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to supervise autonomous AI agent sessions by tailing transcripts, detecting stalls or loops, emitting milestone events for early delivery, querying breaker and subagent telemetry, and tripping the circuit breaker to terminate runaway child processes.MIT
- AlicenseAqualityCmaintenanceEnables coding agents to run persistent, budgeted work sessions with dependency graphs, human decision queues, required validation, and clean handoffs for autonomous or human-in-the-loop execution.16MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive project management and workflow tracking system that integrates with Claude Code via MCP, automatically capturing sessions, tools, agents, and project tasks into a centralized dashboard and database.13 npmMIT
TDQS
Scored across 12 tools
Most tools target distinct operations, but tracking_stop, tracking_kill, tracking_delete, tracking_complete, and tracking_error form a cluster of lifecycle-ending actions that could be confused, though descriptions do differentiate them (SIGTERM+pause vs SIGKILL+delete vs delete vs complete). tracking_update vs tracking_log also slightly overlap since update can carry a message.
Nearly all tools use a consistent snake_case tracking_verb pattern (create, update, log, complete, error, get, list, delete, stop, kill). The single outlier is open_tracking_ui, which uses a different prefix style, a minor deviation.
12 tools is well within the ideal 3-15 range and each maps to a meaningful lifecycle operation for session management. No filler tools appear present.
Full lifecycle coverage exists: create, update, log, complete, error, get, list, delete, stop, kill, plus templates and UI. The main gap is an explicit resume/un-pause operation, since tracking_stop leaves a session paused with no dedicated tool to restart it.