team-tracker-mcp
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| assign_taskC | Create a new task and assign it to one or more team members |
| update_taskC | Update an existing task's status, priority, description, or other fields |
| reassign_taskB | Reassign a task to different team members. Generates handoff context. |
| list_tasksB | List tasks, optionally filtered by assignee, status, priority, or tag |
| link_branchC | Associate a git branch with a task |
| create_subtasksB | Add subtasks to a task. Can be used to break a task into smaller pieces. |
| team_overviewB | Get a snapshot of what everyone on the team is currently working on — active tasks, branches, recent commits |
| get_activityB | Get detailed activity for a specific team member or branch, including commits, files changed, and time range |
| track_branchesA | Fetch all remote branches, scan for new commits, and update task activity. Call this to refresh branch data. |
| detect_conflictsB | Compare active branches against each other and main to detect potential merge conflicts early |
| review_codeB | Get the full diff and stats for a branch or task for code review. Returns the diff against main so Claude can analyze it for quality, bugs, and conflicts. |
| compare_branchesB | Compare two branches — show overlapping files and the diff between them |
| daily_summaryB | Generate an end-of-day summary of what everyone on the team did today — commits, tasks, activity, and concerns |
| generate_feedbackA | Generate unbiased, data-driven feedback for a team member based on their recent git activity, task completion, and code patterns. Returns raw data for Claude to analyze and provide suggestions. |
| nudge_memberB | Send a notification to a team member requesting a status update on a specific task or in general |
| check_notificationsA | Check for pending notifications for the current user. Auto-called on session start. |
| clear_notificationsA | Mark all notifications as read for the current user |
| sync_nowA | Force an immediate sync of .tasks/ changes to the remote repository (commit + push) |
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 18 tools
Most tools have clearly distinct purposes, such as task management, branch tracking, and team summaries. However, review_code, compare_branches, and detect_conflicts all analyze branches and could overlap in purpose, requiring careful reading to distinguish.
The naming is mostly consistent with a verb_noun pattern (assign_task, update_task, get_activity, etc.). A few names like team_overview and daily_summary deviate by being noun phrases, but remain readable and descriptive.
With 18 tools, the count is slightly heavy but reasonable for a comprehensive team and task management server. Each tool appears to earn its place, covering tasks, branches, notifications, and summaries.
The toolset covers core task lifecycle (create, update, reassign, list) and branch integration well. Minor gaps exist, such as a dedicated delete_task or get_task tool, but most workflows are supported. Notifications and syncing round out the surface.