team-tracker-mcp
Integrates with Git repositories for branch tracking, conflict detection, and activity monitoring.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@team-tracker-mcp what is Devyansh working on today?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
team-tracker-mcp
MCP server for team task tracking, code review, and activity monitoring via Claude Code.
Assign tasks, track what everyone is doing across branches, review code, detect merge conflicts early, and get daily summaries — all through natural language in Claude Code.
Setup
1. Add to your project's .mcp.json
{
"mcpServers": {
"team-tracker": {
"command": "npx",
"args": ["-y", "team-tracker-mcp"]
}
}
}Or for local development:
{
"mcpServers": {
"team-tracker": {
"command": "node",
"args": ["/path/to/team-tracker-mcp/dist/index.js"]
}
}
}2. Add to .gitignore
.tasks/.watcher.lock
.tasks/.last-scan3. Start using it
Open Claude Code in your project. The server auto-initializes a .tasks/ directory on first run. Team members are auto-registered from their git identity.
Related MCP server: ProPlan
What it does
Task Management — "assign Devyansh the image queue feature", "mark image queue task as done", "what tasks are assigned to Devyansh?"
Monitoring — "what's everyone working on?", "what did Devyansh do today?", "refresh branch activity"
Code Review — "review Devyansh's code on image-queue", "compare Devyansh's branch with Aman's"
Feedback — "give me today's summary", "generate feedback for Devyansh this week", "ping Devyansh for update"
Notifications — "do I have any notifications?", "clear my notifications", "sync tasks now"
How it works
Data stored in
.tasks/directory in your repo (JSON files, one per task)Synced between team members via normal git push/pull
Background watcher polls remote branches, auto-detects stale tasks and merged branches
Team members identified by git email/username
Leader election ensures only one watcher runs across multiple Claude Code sessions
Tools (18 total)
Category | Tools |
Task Management |
|
Monitoring |
|
Code Review |
|
Feedback |
|
Notifications |
|
Development
npm install
npm run dev # Watch mode with tsx
npm run build # TypeScript compilation
npm start # Run built serverAvailable Tools
18 toolsassign_taskC
Create a new task and assign it to one or more team members
Inputs: title (required), assignees (required), tags, source, +3 more.
check_notificationsA
Check for pending notifications for the current user. Auto-called on session start.
Inputs: no named parameters.
clear_notificationsA
Mark all notifications as read for the current user
Inputs: no named parameters.
compare_branchesB
Compare two branches — show overlapping files and the diff between them
Inputs: branch_a (required), branch_b (required).
create_subtasksB
Add subtasks to a task. Can be used to break a task into smaller pieces.
Inputs: task_id (required), subtasks (required).
daily_summaryB
Generate an end-of-day summary of what everyone on the team did today — commits, tasks, activity, and concerns
Inputs: date.
detect_conflictsB
Compare active branches against each other and main to detect potential merge conflicts early
Inputs: no named parameters.
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.
Inputs: member (required), days.
get_activityB
Get detailed activity for a specific team member or branch, including commits, files changed, and time range
Inputs: date, branch, member.
link_branchC
Associate a git branch with a task
Inputs: branch (required), task_id (required).
list_tasksB
List tasks, optionally filtered by assignee, status, priority, or tag
Inputs: tag, status, assignee, priority.
nudge_memberB
Send a notification to a team member requesting a status update on a specific task or in general
Inputs: member (required), message, task_id.
reassign_taskB
Reassign a task to different team members. Generates handoff context.
Inputs: task_id (required), new_assignees (required), handoff_notes.
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.
Inputs: branch, task_id.
sync_nowA
Force an immediate sync of .tasks/ changes to the remote repository (commit + push)
Inputs: no named parameters.
team_overviewB
Get a snapshot of what everyone on the team is currently working on — active tasks, branches, recent commits
Inputs: no named parameters.
track_branchesA
Fetch all remote branches, scan for new commits, and update task activity. Call this to refresh branch data.
Inputs: no named parameters.
update_taskC
Update an existing task's status, priority, description, or other fields
Inputs: task_id (required), tags, title, status, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
A MCP server built for developers enabling Git based project management with project and personal…
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
AI-native Kanban board — connect Claude to claim, work and move your tasks over MCP.
One MCP server for all your work accounts: Slack, Teams, Google Chat, Jira, ClickUp, digest, tasks.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.4776 npm2Apache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP server for project planning inside Claude. It tracks progress, knows your codebase, and resumes exactly where you left off every session.9 npm5-
- AlicenseNot gradedqualityCmaintenanceMCP server that watches issue trackers and comments for 'Dear Claude' and spawns local Claude Code instances to execute tasks, posting results back to the original platform.84 npmMIT
- AlicenseAqualityDmaintenanceAn MCP server that gives Claude live access to your GitHub workspace — PR reviews, issue triaging, repo search, and weekly digest reports through natural language.7MIT