This read-only DevTrack MCP server lets you inspect development context, commits, tickets, pending actions, EOD drafts, and voice profiles, but not approve or modify DevTrack data.
Get your active work context: active ticket, repo path, today's commit count, and ticket-mapping confidence.
Get an end-of-day summary draft grouped by ticket for standups/daily reports.
Inspect the pending actions queue, including confidence scores and expiry times.
Get full context for a specific ticket: recent commits, pending actions targeting it, and last activity.
Get today's commits grouped by ticket, optionally filtered by repository path.
Get the inferred voice/writing-style profile for contexts like commits, comments, reports, tasks, or ticket mapping.
Comment on issues/PRs, sync recent activity, and alert on review requests.
Comment on issues; list, view, create, and sync issues through the Go connector.
Supports posting commit comments and transitioning tickets, with server-side webhook integration for PM workflows.
Never write a standup again.
DevTrack watches your Git work, connects it to tickets, and prepares status updates and end-of-day reports in the background. It is local-first, offline-capable, and stages outbound actions for your review.
Website · Download · Documentation · Latest release
Mogrov owns the DevTrack landing page, wiki, privacy page, and installer scripts. This repository owns the product code and GitHub releases.
Related MCP server: devrecall
Observes commits without interrupting or replacing normal Git commands.
Reports completed work without tracking hours or time spent per task in the v3.3.0 development line.
Maps ticket-named branches such as feature/AUTH-42-refresh-token to work items.
Builds reviewable ticket updates and end-of-day reports from the work already completed.
Keeps its client-side source of truth in local SQLite and uses Ollama by default for local AI.
Shares current work and DevTrack Sage knowledge with compatible assistants through ten read-only MCP tools.
Nothing is posted merely because DevTrack generated it. PM updates, transitions, and deliveries are placed in a pending-actions queue before delivery; configured earned auto-approval rules can advance eligible actions. Anonymous telemetry is also opt-in and disabled by default.
DevTrack supports Windows, macOS, and Linux. Git is required. The core Go client, SQLite storage,
Git observation, queue, and MCP features do not require Python or an AI model. Managed AI features
add uv, PostgreSQL, and an LLM provider; Ollama is the default.
Use the Mogrov download link, or install the latest stable release directly:
Linux or macOS
curl -fsSL https://mogrov.com/downloads/devtrack/install.sh | shWindows PowerShell
irm https://mogrov.com/downloads/devtrack/install.ps1 | iexManual binaries and checksums are available on GitHub Releases.
Stable v3.2.0 retains the former time-tracking behavior. The fixes and removal are on dev at
860b91b, prepared for v3.3.0; rolling development builds use dev-<commit>. A push to dev does
not upgrade an installed binary or publish a new stable release. See the
development release notes and qualification plan.
devtrack versionRun setup from the Git repository you want DevTrack to observe:
cd /path/to/your/repository
devtrack setup
devtrack start
devtrack status
devtrack doctorThe setup wizard configures the operating mode, repository, LLM, identity, and optional PM
integration. Choose none for the PM integration when evaluating the local-only path. Managed mode
requires PostgreSQL for the optional Python service; Go-native features remain available while that
service and the model are being prepared.
Managed mode starts the local Python server for AI-written ticket comments, EOD narratives,
Boardroom reviews, planning, and voice personalization. External mode does not start Python: point
DEVTRACK_SERVER_URL at a separately operated Python/PostgreSQL server for those features. With no
server reachable, commit capture, deterministic ticket mapping, local history, queue, and MCP still
work; generated reports and other server-backed features are unavailable. Model failures on a
reachable server fall back to raw or templated wording. External mode skips automatic first-run
voice mining. See the LLM guide.
Use a ticket-named branch and commit normally:
git switch -c feature/AUTH-42-refresh-token
git commit -m "fix auth redirect"
devtrack logs
devtrack queue
devtrack eodqueue lets you inspect staged actions before approving anything. See the
Quick Start for the complete first-run walkthrough.
In the development line, capture enumerates unseen commits across local branch tips, so rapid commits and switching branches during processing are included. Keep the daemon running: existing history is seeded at startup, and catch-up for commits made while it was stopped is not guaranteed.
devtrack work start AUTH-42 selects fallback ticket context; work stop clears it and work status
shows it. These commands do not start or stop timers. devtrack work report generates a commit-based
EOD report through the configured server.
Incidents, stories, bugs, and tasks all map by their work-item reference: for example, a Jira
incident hotfix/OPS-123-restore-login, Azure DevOps story feature/ADO-456-add-export, or
GitHub issue fix/GH-42-handle-timeout. The PM system supplies the item type; the branch kind
does not. A canonical branch wins over an explicit commit reference, which wins over selected
ticket context. Run devtrack ticket convention and devtrack ticket check <branch> to inspect
the rule, or devtrack ticket link <commit-hash> <ticket-ref> to correct an observed mapping.
See work-item and ticket mapping for configuration, conflicts, and examples.
devtrack eod status and devtrack eod show read the latest report across local and server history.
devtrack queue list --all shows recent actions from both stores. Server actions use IDs such as
server:123: pass that full ID to queue approve, queue reject, or queue edit. Bare numeric IDs
address local actions. An unavailable server is reported explicitly.
Add DevTrack's read-only MCP server to the current project:
devtrack mcp setup
devtrack mcp test
devtrack mcp statusReload your MCP-capable assistant after setup. It can then read current ticket context, commits, pending actions, EOD context, voice information, and published Sage knowledge. MCP cannot approve actions or modify DevTrack data.
DevTrack Sage captures useful command activity from supported coding harnesses and turns repeated work into searchable local Markdown knowledge:
devtrack sage status
devtrack sage search "docker compose"
devtrack sage topicsLearn more in MCP and Agent Memory and DevTrack Sage.
I want to… | Guide |
Install or upgrade DevTrack | |
Complete the first-run workflow | |
Understand deployment choices | |
Configure repositories, integrations, or models | |
Find a command | |
Connect an AI assistant | |
Use local command knowledge | |
Fix an installation or runtime problem | |
Review privacy and data flow | |
Qualify automatic capture and reporting | |
Map incidents, stories, bugs, and tasks | |
Review the v3.3.0 development boundary |
Contributors and maintainers can start with the repository documentation map and architecture.
The default Go, SQLite, and Ollama path stays local. External PM systems, delivery channels, and
cloud LLMs receive data only when configured for the corresponding operation. Telemetry remains off
until explicitly enabled with devtrack telemetry on. Read the full
privacy guide before enabling external services.
DevTrack uses the DevTrack Community License: free for personal use and teams of up to 10 users; larger teams and hosted use require an enterprise license.
Returns the developer's current active ticket, repo path, today's commit count, and confidence in the ticket mapping. This is the primary context tool — call it first.
Inputs: no named parameters.
Returns today's EOD narrative draft — a summary of the day's commits grouped by ticket, suitable for a standup or daily report. Template-based (no LLM required).
Inputs: no named parameters.
Returns the current pending actions queue — actions DevTrack wants to take but hasn't yet. Each action has a confidence score and an expiry time.
Inputs: no named parameters.
Returns full context for a named ticket: recent commits, current pending actions targeting it, and its last activity time.
Inputs: ticket_id (required).
Returns all commits from today, grouped by ticket ID, with message and metadata.
Inputs: repo_path.
Returns the developer's inferred writing style profile for a given context type. Use this to understand how the developer prefers to communicate before generating text on their behalf.
Inputs: context_type.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 6 tools
Each tool has a distinct purpose: active context, EOD summary, pending actions, ticket context, today's commits, and voice profile. Some overlap exists around commit data, but the descriptions clearly differentiate raw commits, summaries, and ticket-specific views.
All tool names follow a consistent get_<noun> pattern with clear, descriptive suffixes. There is no mixing of naming conventions or vague verb choices.
With 6 tools, the set is well-scoped for a developer-context server. Each tool covers a meaningful slice of the domain without unnecessary bloat.
The read-only context domain is well covered: active state, daily commits, pending actions, ticket details, EOD summary, and communication style. There is no obvious missing getter, though a way to browse historical days or all tickets could be considered a minor gap.
Opinionated sprint tracker. Read/update tickets, sprints, velocity from Claude/Cursor/Zed.
Privacy-first work tracking with summaries, reports, coaching, and AI-ready long-term memory.
AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools).
30+ deterministic dev and delivery tools: linting, metrics, diagrams, model advice, AI-text checks.
