# GitScrum Time Tracking MCP > GitScrum Time Tracking lets you manage project budgets, log billable hours, and get team productivity reports all through conversation. Start timers directly from your agent, review budget burn-down charts, or instantly pull daily standup summaries without opening a single dashboard. ## Overview - **Category:** productivity - **Price:** Free - **Tags:** time-tracking, budget-monitoring, standup-automation, productivity-analytics, burn-down-charts, team-reports, billable-hours ## Description This MCP handles the messy parts of project work. Instead of jumping between Jira, Slack, and Excel to track who did what, when they did it, and if you're over budget, you just talk to your agent. You can ask it to start a timer on a task or ask for a summary of blockers from yesterday’s standup. It handles the back-and-forth logging so you don't have to worry about remembering to manually log time at the end of the day. If you need deep insight into team performance, the Vinkius catalog makes it easy to connect this tool and get instant visibility into project health—whether that’s checking overall budget consumption or reviewing individual contributor scores. ## Tools ### budget_alerts Checks if a project is nearing a financial threshold and alerts you. ### budget_burndown Generates charts showing how quickly the project budget is being spent over time. ### budget_consumption Provides a breakdown of how the total allocated budget has been used. ### budget_events Lists all historical events that affected the project's budget. ### budget_overview Gives a high-level summary of a project’s current financial status and allocated funds. ### projects_at_risk Identifies which projects are currently consuming funds too fast or are nearing budget limits. ### my_tasks Lists all tasks assigned to you across different projects and workspaces. ### standup_blockers Lists all current roadblocks, technical dependencies, or required approvals holding up project work. ### completed_yesterday Lists all tasks that were marked as finished on the previous day. ### contributors Summarizes who has been most active and productive within a specified time period. ### weekly_digest Compiles a summary of the team's activities and achievements from the past week. ### stuck_tasks Identifies tasks that have been in an 'in-progress' state for too long without movement. ### standup_summary Provides a comprehensive overview of the daily standup meeting results. ### team_status Retrieves the current availability and working status of all team members. ### get_task Verifies a task's existence and retrieves its specific details using a unique identifier. ### list_tasks Provides a list of project tasks, allowing you to filter by status like 'todo' or 'in-progress'. ### my_today_tasks Gets a list of all tasks that are due for completion today. ### get_active_timer Retrieves details about any timer that is currently running right now. ### time_analytics Provides deep, statistical analysis of all recorded project time entries and usage patterns. ### delete_time_entry Removes specific, incorrect time entries from the tracking record. ### list_time_entries Fetches all recorded time entries for a specific project. ### log_manual_time Creates a new time entry record, useful for logging hours worked at a later date. ### productivity_report Generates a general report summarizing individual and team productivity scores over time. ### time_reports Generates comprehensive reports covering multiple dimensions of time spent. ### start_timer Activates a timer for a specific task, automatically tracking time until you tell it to stop. ### stop_timer Stops the currently running timer and records the elapsed time. ### team_time_report Generates a detailed report showing how much time the entire team spent on specific projects. ### time_timeline Presents a chronological, day-by-day view of all recorded activity and time entries. ## Prompt Examples **Prompt:** ``` Start a timer on task WEB-42 in the web-app project. ``` **Response:** ``` Timer started on WEB-42: 'Implement user authentication' at 10:23 AM. Timer ID: tt-4521. I'll track until you ask me to stop. Say 'stop timer' when you're done, and I'll record the elapsed time automatically. ``` **Prompt:** ``` Give me the standup summary for today. ``` **Response:** ``` Today's standup: 14 tasks completed yesterday (5 by johndoe, 4 by janedoe, 3 by alexdev, 2 by sarahpm). 8 tasks in progress. 2 blockers flagged: WEB-38 (waiting on API credentials, 3 days blocked) and WEB-45 (design review pending). Participation: 100%. Shall I dig into the blockers? ``` **Prompt:** ``` Which projects are at budget risk? ``` **Response:** ``` 2 projects flagged: 1) 'Mobile App v2' — 92% consumed ($46,000 of $50,000), burn rate $2,300/week, estimated overshoot in 5 days. 2) 'API Redesign' — 78% consumed with sprint scope creep detected. Want me to show the burn-down chart or set up budget alerts? ``` ## Capabilities ### Track time with active timers Start and stop timers on specific tasks using a simple command, automatically logging elapsed time. ### Analyze project budgets Review budget health by generating burn-down charts, checking consumption breakdowns, or getting immediate alerts when spending nears thresholds. ### Automate daily standups Get a structured summary of team activity, including tasks completed yesterday and any current blockers preventing progress. ### Review historical time logs Access detailed lists or timelines of past time entries for specific projects or across the entire portfolio. ### Measure team performance Pull productivity reports and contributor activity summaries, filtered by week, month, or quarter. ## Use Cases ### Project Manager needs budget status. The PM opens their agent and asks, 'Which projects are over budget?' The agent immediately runs `projects_at_risk` and delivers a list of the top two offenders, complete with burn-down data. ### Developer needs to log time retroactively. A developer realizes they spent three hours on a bug fix last week. Instead of opening a sheet, they simply ask their agent to `log_manual_time` for the specific project and time block. ### Team Lead needs blockers identified. It's Monday morning. The team lead asks, 'What are our current roadblocks?' The agent runs `standup_blockers` and provides a clear list of tasks stuck waiting on API credentials or design sign-off. ### Client needs full project history. A client asks for proof of hours spent last quarter. You ask the agent to generate `time_reports` for the entire period, giving them a clean, verifiable timeline. ## Benefits - Stop manually creating standup reports. Ask the agent for a `standup_summary` and get yesterday's completions, current blockers, and task status in seconds. - Never worry about exceeding budget again. Running `projects_at_risk` gives you an immediate warning, showing exactly which projects are spending too fast. - Eliminate context switching. Start or stop a timer right from your chat; the agent handles the tracking for you so you don't have to remember to log time. - Review team performance instantly using `team_time_report` and `contributors`. You get clear data on who is spending time where, helping you balance workloads. - Go beyond simple task lists. Use `time_analytics` to see deep usage patterns, understanding not just *what* work was done but *how efficiently* it was done. ## How It Works The bottom line is, it turns complex dashboard navigation into simple conversation. 1. Subscribe to the GitScrum Time Tracking MCP in Vinkius and provide your API token and company slug. 2. Tell your agent what you need—for example, 'Start a timer on task WEB-42' or 'Show me budget alerts for Project Alpha.' 3. The MCP executes the request, pulling real data into your chat window so you get an immediate answer without leaving your workflow. ## Frequently Asked Questions **How do I use `start_timer` to track my work?** Just tell your agent, 'Start a timer for X task.' The MCP activates the timer on that specific task. When you're finished, ask it to stop the timer. **What is `budget_burndown` and when should I use it?** `budget_burndown` shows how fast your money is going relative to time left on the project. Use this when you need a visual warning about potential overspending. **How do I run a standup summary using `standup_summary`?** Simply ask for 'today's standup summary.' The MCP pulls data on who finished tasks yesterday, what's currently stuck, and flags any immediate blockers. **What if I need to correct an old time entry? Do I use `delete_time_entry`?** Yes. If you logged hours for the wrong day or task, you can run `delete_time_entry` to remove it from the record. You'll then log the correction using `log_manual_time`. **Can I check my tasks assigned to me with `my_tasks`?** Yes, running `my_tasks` gives you a complete list of every task currently assigned to your name across all projects in the system. **How do I filter my past time logs for a specific period using the `list_time_entries` tool?** You pass explicit parameters, like start and end dates, or a project ID to refine your search. This lets you pull reports for a single sprint or month without manually sorting through years of data. **How do I get an aggregated view of team activity over time using the `contributors` tool?** You specify the desired period, such as 'week', 'month', or 'quarter', within your MCP call. The system then compiles and summarizes contribution scores for every member across that defined scope. **How do I set up automated warnings when a project approaches its limit using `budget_alerts`?** You define specific monetary thresholds or percentage limits in the tool. The MCP monitors consumption and triggers an alert immediately when the budget crosses that predefined risk level, giving you advance notice. **Can the agent start and stop timers on tasks without me opening GitScrum?** Yes! Use `start_timer` with any task UUID to begin tracking, and `stop_timer` to end it. Only one timer can be active at a time. Use `list_tasks` or `my_today_tasks` first to find the task you want to track. The agent handles the complete flow in seconds. **Can I get a standup summary without attending the meeting?** Absolutely. Use `standup_summary` for the daily overview, `completed_yesterday` for what the team shipped, `standup_blockers` for current impediments, and `team_status` for per-member breakdown. It's your entire standup in 4 quick queries. **Can the agent flag projects that are over budget?** Yes. Use `projects_at_risk` to see all projects approaching or exceeding their budget threshold. Then drill into any project with `budget_overview` for total vs consumed, `budget_burndown` for trend analysis, and `budget_alerts` for active threshold warnings.