DevTrack MCP server
Commit Nov 1, 2026Lets an AI client read local work context, Git commits, ticket mappings, and searchable command knowledge via read-only MCP tools.
Also known as sraj0501/Devtrack_
- Stars
- 2
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 3.2.0
- Last commit
- Nov 1, 2026
- License
- —
What is DevTrack MCP?
DevTrack lets an AI client read local work context, Git commits, ticket mappings, and searchable command knowledge via read-only MCP tools.
Summary generated from the project's README
About DevTrack MCP server
Automating status updates and end-of-day reports by connecting Git activity to project management tickets is what DevTrack enables. This local-first tool observes your commits and maps ticket-named branches, such as those for Jira or GitHub issues, to specific work items. It uses a local SQLite database for storage and can utilize Ollama for local AI processing, ensuring your development context remains private.
Developers use the ten read-only MCP tools to share work context with AI assistants. These tools allow an agent to inspect current ticket context, recent commits, pending actions in the queue, and end-of-day narratives. The system also includes DevTrack Sage, which converts repeated command activity into searchable Markdown knowledge. While the core Git observation and MCP features work entirely offline, managed mode can connect to a Python and PostgreSQL server to enable AI-written ticket comments and planning features.
What you can do with it
- 1Generate daily status reportsAsk your AI assistant to summarize your recent Git commits into a professional end-of-day report.
- 2Retrieve command knowledgeSearch for specific technical workflows or command sequences that you have used previously.
- 3Review pending updatesHave an AI agent check the queue of staged project management updates before they are sent.
- 4Map branches to ticketsVerify that your current feature branch is correctly linked to the intended work item.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablesraj0501/devtrack_ is public and reachablegithub.com/sraj0501/devtrack_ ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-01github.com/sraj0501/devtrack_ ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubDevTrack
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

Website and documentation
Mogrov owns the DevTrack landing page, wiki, privacy page, and installer scripts. This repository owns the product code and GitHub releases.
What DevTrack does
- 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-tokento 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.
Get started
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.
1. Install
Use the Mogrov download link, or install the latest stable release directly:
Linux or macOS
curl -fsSL https://mogrov.com/downloads/devtrack/install.sh | sh
Windows PowerShell
irm https://mogrov.com/downloads/devtrack/install.ps1 | iex
Manual 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 version
2. Configure a repository
Run setup from the Git repository you want DevTrack to observe:
cd /path/to/your/repository
devtrack setup
devtrack start
devtrack status
devtrack doctor
The 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.
3. Try the workflow
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 eod
queue 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.
Agent memory and DevTrack Sage
Add DevTrack's read-only MCP server to the current project:
devtrack mcp setup
devtrack mcp test
devtrack mcp status
Reload 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 topics
Learn more in MCP and Agent Memory and DevTrack Sage.
Where to go next
| I want to… | Guide |
|---|---|
| Install or upgrade DevTrack | Download |
| Complete the first-run workflow | Quick Start |
| Understand deployment choices | Installation |
| Configure repositories, integrations, or models | Configuration |
| Find a command | CLI Reference |
| Connect an AI assistant | MCP and Agent Memory |
| Use local command knowledge | DevTrack Sage |
| Fix an installation or runtime problem | Troubleshooting |
| Review privacy and data flow | Privacy |
| Qualify automatic capture and reporting | Basic workflow testing |
| Map incidents, stories, bugs, and tasks | Work-item and ticket mapping |
| Review the v3.3.0 development boundary | Development release notes |
Contributors and maintainers can start with the repository documentation map and architecture.
Privacy
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.
License
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.
DevTrack MCP questions
Can the MCP server modify my DevTrack data?
No, the MCP integration provides read-only access to your work context and knowledge.
What kind of information can an AI assistant access through MCP?
An assistant can read current ticket context, commits, pending actions, end-of-day context, voice information, and published Sage knowledge.
Does DevTrack require an internet connection or cloud AI?
It is local-first and offline-capable, using SQLite for storage and Ollama for local AI by default.