Devtrack MCP Server
Related Servers
Alternatives to Devtrack MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server that turns your IDE session history and git activity into Azure DevOps ticket updates, drafting comments, hours, and state changes with confirm-before-post. It also provides read-only progress, people, breakdown, and timeline reports for leads.MIT
- AlicenseAqualityAmaintenanceLocal-first dev memory: indexes Git commits, PRs, Jira/Linear tickets, Confluence docs, Slack threads, and Calendar events into a local SQLite/FTS5/ONNX index, and exposes them as MCP tools so Claude Code, Cursor, and Codex can search and cite your past work.174MIT
- AlicenseAqualityDmaintenanceA unified developer toolkit for AI-assisted workflows. Task timing, doc drift detection, env validation, secret scanning, port conflict resolution, AI context generation, and license auditing — one MCP server, one install.73MIT
- FlicenseNot gradedqualityAmaintenanceLocal MCP server that lets your AI coding agent query its own cross-tool project history - file/command freshness, past test failures, cost & token spend, cache status, and session handoff - over stdio, 100% local, no telemetry.48-
- AlicenseBqualityAmaintenanceSelf-hosted issue tracker built for agent-driven development. One binary, SQLite storage, MCP-native, with a web UI, REST API, and CLI for the humans.2765Apache 2.0
- AlicenseNot gradedqualityCmaintenanceDeveloper Knowledge OS — local-first bimodal workspace for humans (TUI) and AI agents (MCP). Manage Git repos, vault notes, and assets with 19 MCP tools including unified project context queries.AGPL 3.0
TDQS
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.