Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Read local work context and published Sage command knowledge over MCP.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account sraj0501, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (3.2.0) reached the registry 16 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
feature/AUTH-42-refresh-token to work items.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 | 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- . 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
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.
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 to inspect the rule, or devtrack ticket link 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 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.
| 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.
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.