# GitScrum Time Tracking MCP for AI Agents AI Agent Connect > GitScrum Time Tracking. Track time, budgets, and project progress directly from your AI client. Start timers, log hours, check budget burn-down, and pull standup summaries to keep your team on track without switching tabs. ## Overview - **Category:** productivity - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_2iGgDQUCIaLPRgPaZwgFAGAHENxVPaHPC9D81h7y/ai-agent-connect - **Tags:** time-tracking, budget-monitoring, standup-automation, productivity-analytics, burn-down-charts, team-reports, billable-hours ## Description Managing project time and budgets usually feels like a chore. You're constantly jumping between your IDE, your browser, and a time-tracking dashboard just to make sure everyone is logging their hours correctly. GitScrum Time Tracking changes that by bringing all your project data directly into your chat interface. Instead of hunting for a project's health or manually entering a two-hour block for a bug fix, you just tell your agent what to do. It handles the heavy lifting of recording entries, checking budget thresholds, and pulling together status updates for your morning meetings. This Connector is part of the Vinkius catalog, which makes it easy to plug into your existing workflow. You get a clear view of who's working on what and how much of the budget is left without ever leaving your workspace. It's about getting back to the actual work while the agent keeps the administrative side of the project running in the background. ## Tools ### my_tasks Find tasks assigned to you across all your different workspaces. This makes it easy to see what you need to work on next. ### budget_alerts See notifications for when a budget hits a specific threshold. This prevents unexpected overages. ### budget_burndown Get the data needed to visualize how fast the budget is being spent. Use this to forecast project end dates. ### budget_consumption See a breakdown of how the budget is being used. This helps you understand which features are costing the most. ### budget_events View a log of all budget related events and changes. This provides a history of all financial adjustments. ### budget_overview Get a high-level look at your project's current budget. This helps you see the total remaining funds at a glance. ### projects_at_risk See which projects are heading toward a budget overage. This helps you prioritize which projects need attention. ### standup_blockers Identify the specific issues currently stopping team progress. Use this to clear the path for your team. ### completed_yesterday See a list of everything your team finished in the last 24 hours. This is great for quick status checks. ### contributors Get a summary of activity for specific people over a chosen period. This helps you see who is doing the heavy lifting. ### weekly_digest Receive a summary of activity for the past week. Use this to see how the team performed over several days. ### stuck_tasks Find tasks that haven't moved in a while and need attention. This helps you identify bottlenecks quickly. ### standup_summary Get a quick overview of the team's daily progress and blockers. This replaces manual status reporting. ### team_status Check the current status of every team member. Use this to see who is available or busy. ### get_task Look up specific details for a task using its unique ID. This is useful for verifying details before starting work. ### list_tasks See a list of project tasks filtered by their current status. This helps you organize your current workflow. ### my_today_tasks See which tasks are due for completion today. This is perfect for planning your daily schedule. ### get_active_timer Check which timer is currently running. This ensures you aren't accidentally running multiple timers. ### time_analytics View data on how time is being spent across the project. This helps you understand where the most effort goes. ### delete_time_entry Remove a specific time entry from the records. Use this to correct any mistakes in your logs. ### list_time_entries See all time tracking entries for a specific project. This provides a full audit trail of project time. ### log_manual_time Create a retroactive time entry for work already finished. This is great for logging tasks done offline. ### productivity_report Get a report on overall team productivity. This provides a high-level view of your team's output. ### time_reports Access detailed reports on time spent on various project elements. Use this for deep dives into project costs. ### start_timer Start a new timer for a specific task. Use this to begin tracking your current work immediately. ### stop_timer End the currently running timer. This ensures your time logs are accurate and capped correctly. ### team_time_report Get a report on how much time team members are spending on work. This helps with capacity planning. ### time_timeline View a chronological list of all time entries. This shows you exactly how time flowed throughout the day. ## Prompt Examples **Prompt:** ``` Which projects are currently at risk of going over budget? ``` **Response:** ``` I've checked the current budget status for your projects. Here is the summary: | Project Name | % Consumed | Burn Rate | Status | | :--- | :--- | :--- | :--- | | **Mobile App v2** | 92% | $2,300/week | ⚠️ At Risk | | **API Redesign** | 78% | $1,500/week | ⚠️ Scope Creep | Would you like me to show the burn-down chart for 'Mobile App v2' or set up a budget_alert for the 90% threshold? ``` **Prompt:** ``` Give me a summary of what the team did yesterday. ``` **Response:** ``` Here is the standup summary for yesterday: **Completed Tasks:** - 14 tasks finished (5 by johndoe, 4 by janedoe, 3 by alexdev, 2 by sarahpm) **Current Blockers:** - **WEB-38**: Waiting on API credentials (Blocked for 3 days) - **WEB-45**: Design review pending **Participation:** 100% ``` **Prompt:** ``` Start a timer for the API integration task. ``` **Response:** ``` Done! I've started a timer for the **API integration** task. - **Timer ID:** tt-9821 - **Status:** Running Just say 'stop timer' when you're finished and I'll log the total time for you. ``` ## Capabilities ### Start and stop timers Begin and end time tracking for specific tasks with one command. ### Log retroactive hours Manually record time entries for work already completed. ### Monitor budget burn-down See how quickly your project budget is being spent in real time. ### Pull automated standups Get a summary of what your team finished and what's currently blocked. ### Analyze team productivity View activity scores and time breakdowns for every contributor. ### Identify stuck tasks Find work items that haven't moved and need immediate attention. ## Use Cases ### Forgetting to start a timer A developer forgets to start a timer when they switch tasks. They ask their agent to start a timer on a specific task ID, and the agent handles the start and stop commands. ### Checking budget during a meeting A project manager needs to know if a project is over budget during a meeting. They ask the agent for a budget_overview and projects_at_risk to get immediate numbers. ### Automating daily standups Team leads spend too much time manually compiling standup notes. They ask for a standup_summary to see what was finished and what's blocked automatically. ### Identifying team bottlenecks A manager wants to see if a specific team member is overloaded. They use contributors and team_time_report to see a breakdown of work for the last week. ## Benefits - Stop context switching by using start_timer and stop_timer directly within your IDE or chat client. - Keep projects on track by monitoring budget_burndown and budget_alerts to prevent overspending. - Save time on meetings by pulling standup_summary and completed_yesterday data instantly. - Identify bottlenecks faster by querying stuck_tasks and standup_blockers to clear the path for your team. - Get a clearer picture of workload by viewing my_today_tasks and my_tasks across all workspaces. - Analyze team performance with time_analytics and productivity_report to make data-driven decisions. ## How It Works The bottom line is that you can manage your project's time and budget through conversation rather than manual data entry. 1. Connect your GitScrum API token and company slug to the Connector. 2. Ask your agent to start a timer, log a manual entry, or pull a report. 3. Receive real-time updates on time logs and project health. ## Frequently Asked Questions **How does GitScrum Time Tracking help with project budgets?** It gives you instant visibility into your spending. You can ask your agent to pull budget overviews or check for projects at risk, helping you catch overages before they happen. **Can I use this to see my own tasks?** Yes, you can ask your agent to list your tasks or show what's due today. It pulls this data from all your workspaces so you don't have to hunt for it. **How does this help with daily standups?** It automates the boring part of meetings. Your agent can pull a summary of completed tasks and current blockers, giving you a ready-to-use report in seconds. **Can I log time for work I did yesterday?** Absolutely. You can tell your agent to log a manual time entry for any past work, and it will record the correct timestamps and descriptions for you. **How do I see who is currently blocked?** You can ask your agent to identify blockers or stuck tasks. It will scan your project data and tell you exactly what's holding up progress. **Does this help with team productivity reports?** Yes, it provides deep insights. You can request productivity reports or weekly digests to see how the team is performing and where time is being spent. **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.