team-tracker-mcp
# 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`
```json
{
"mcpServers": {
"team-tracker": {
"command": "npx",
"args": ["-y", "team-tracker-mcp"]
}
}
}
```
Or for local development:
```json
{
"mcpServers": {
"team-tracker": {
"command": "node",
"args": ["/path/to/team-tracker-mcp/dist/index.js"]
}
}
}
```
### 2. Add to `.gitignore`
```
.tasks/.watcher.lock
.tasks/.last-scan
```
### 3. 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.
## 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 | `assign_task`, `update_task`, `reassign_task`, `list_tasks`, `link_branch`, `create_subtasks` |
| Monitoring | `team_overview`, `get_activity`, `track_branches`, `detect_conflicts` |
| Code Review | `review_code`, `compare_branches` |
| Feedback | `daily_summary`, `generate_feedback`, `nudge_member` |
| Notifications | `check_notifications`, `clear_notifications`, `sync_now` |
## Development
```bash
npm install
npm run dev # Watch mode with tsx
npm run build # TypeScript compilation
npm start # Run built server
```
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.