Devtrack MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_active_contextA | Returns the developer's current active ticket, repo path, today's commit count, and confidence in the ticket mapping. This is the primary context tool — call it first. |
| get_eod_summaryA | Returns today's EOD narrative draft — a summary of the day's commits grouped by ticket, suitable for a standup or daily report. Template-based (no LLM required). |
| get_pending_actionsA | Returns the current pending actions queue — actions DevTrack wants to take but hasn't yet. Each action has a confidence score and an expiry time. |
| get_ticket_contextA | Returns full context for a named ticket: recent commits, current pending actions targeting it, and its last activity time. |
| get_today_commitsA | Returns all commits from today, grouped by ticket ID, with message and metadata. |
| get_voice_profileA | Returns the developer's inferred writing style profile for a given context type. Use this to understand how the developer prefers to communicate before generating text on their behalf. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.