DevTrack MCP server

DevTrack

Never write a standup again.

You commit. Tickets update, EOD reports write themselves — silently, in your voice, entirely on your machine.

devtrack — a single Go binary. Local-first. Offline by default.

The 30-second pitch

You write code. DevTrack handles the rest.

A background daemon watches your commits and infers everything around them — which ticket you're on (from the branch name), what you did today, what the standup should say. It drafts the ticket comment and the EOD report in your writing voice, learned from your own git history. Your only obligation: name branches with ticket IDs.

Nothing is sent behind your back. Every outbound action — a Jira comment, a ticket transition, an email — is staged in a review queue first. You approve it, or you let it earn auto-approve over time. The daemon never prompts you, never blocks a commit, and never interrupts.

And it's the memory your AI agents lack

Available since v3.1.0: Phase 9 onboarding and the local, read-only MCP server ship in the

latest public release, v3.1.1. Five native MCPB bundles are available for Windows, macOS, and Linux.

Coding agents are session-based: they exist while invoked, then forget. DevTrack is always on. One command —

devtrack mcp setup

— and Claude Code knows your active ticket, today's commits, your pending queue, and how you write. Nothing else runs at 6pm, groups the day's commits by ticket, and has the EOD ready before you ask.

Trust

Local Ollama by default; SQLite on disk. The default daily path stays on your machine. If you configure a PM system, email/chat delivery, an external server, or a cloud LLM, DevTrack sends only the payload needed for that enabled operation. Anonymous usage telemetry is opt-in and off unless you run devtrack telemetry on.

Ten-minute quickstart

The latest public release is v3.1.1. Download the matching platform asset from GitHub Releases, or build from source:

git clone --branch main --single-branch https://github.com/sraj0501/Devtrack_.git
cd Devtrack_/devtrack_client
go build -o devtrack .
sudo install -m 0755 devtrack /usr/local/bin/devtrack

Verify that this is an MCP-capable build, then run setup from the Git repository you want DevTrack to watch. Choose none when asked for a PM integration if you only want to try the local path. Managed mode requires a PostgreSQL URL for the Python service; Ollama remains the default LLM and can finish preparing in the background.

devtrack mcp status           # must report six registered tools
cd /path/to/the/repo/to/watch
devtrack setup

Minute 2: local context, no Python or model required

The Go binary and local SQLite database are ready as soon as setup finishes. Wire the current repository into Claude Code, then exercise the same MCP server locally:

devtrack mcp setup
devtrack mcp test

Reload Claude Code after mcp setup. Its DevTrack tools can now read the active ticket, today's commits, pending actions, voice profile, ticket context, and a template EOD summary. The MCP server runs on demand over stdio; it does not need a background Python process.

Minutes 3–10: start the silent worker

devtrack start
devtrack status
devtrack doctor

Shortened. The full README is on GitHub.