S
sraj0501/Devtrack_
no SECURITY.md
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 2 ★ · sraj0501/Devtrack_ · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 2 ★ · 23 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
sraj0501/Devtrack_;first catalogued 2026-10-23;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# DevTrack
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
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
## 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-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 until approved. 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 guided download page, or install the latest stable
release directly:
Linux or macOS
sh
curl -fsSL https://devtrack.cloud/install.sh | sh
Windows PowerShell
powershell
irm https://devtrack.cloud/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- . A push to dev does
not upgrade an installed binary or publish a new stable release. See the
development release notes and qualification plan.
sh
devtrack version
### 2. Configure a repository
Run setup from the Git repository you want DevTrack to observe:
sh
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.
### 3. Try the workflow
Use a ticket-named branch and commit normally:
sh
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
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
## 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-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 until approved. 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 guided download page, or install the latest stable
release directly:
Linux or macOS
sh
curl -fsSL https://devtrack.cloud/install.sh | sh
Windows PowerShell
powershell
irm https://devtrack.cloud/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- . A push to dev does
not upgrade an installed binary or publish a new stable release. See the
development release notes and qualification plan.
sh
devtrack version
### 2. Configure a repository
Run setup from the Git repository you want DevTrack to observe:
sh
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.
### 3. Try the workflow
Use a ticket-named branch and commit normally:
sh
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
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/sraj0501-devtrack/)
- Source
- awesome · https://github.com/sraj0501/Devtrack_
- Browse by field
- MCP servers
- Traction
- 2 ★
- Listed by
- 23 independent sources
- added
- today
- Security policy
- no
SECURITY.mdat the repository root (which does not mean it is unsafe)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.