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.

GitScrum Time Tracking MCP Server for VS Code Copilot 28 tools — connect in under 2 minutes

Name: GitScrum Time Tracking
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 28 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install GitScrum Time Tracking and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "gitscrum-time-tracking": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About GitScrum Time Tracking MCP Server

What you can do

Live time tracking — start, stop, and manage timers on any task with one command
Manual time logging — record retroactive time entries with exact start/end timestamps and descriptions
Productivity analytics — access team reports, individual productivity scores, and timeline visualizations
Budget monitoring — check budget burn-down, consumption breakdowns, risk alerts, and project budget health
Daily standups — get automated standup summaries, yesterday's completions, current blockers, and stuck tasks
Team insights — review contributor activity scores, weekly digests, and per-member time breakdowns

GitHub Copilot Agent mode brings GitScrum Time Tracking data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 28 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

The GitScrum Time Tracking MCP Server exposes 28 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect GitScrum Time Tracking to VS Code Copilot via MCP

Follow these steps to integrate the GitScrum Time Tracking MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using GitScrum Time Tracking

Ask Copilot: "Using GitScrum Time Tracking, help me...". 28 tools available

Why Use VS Code Copilot with the GitScrum Time Tracking MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with GitScrum Time Tracking through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

GitScrum Time Tracking + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the GitScrum Time Tracking MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

GitScrum Time Tracking MCP Tools for VS Code Copilot (28)

These 28 tools become available when you connect GitScrum Time Tracking to VS Code Copilot via MCP:

budget_alerts

Get budget threshold alerts

budget_burndown

Get budget burn-down chart data

budget_consumption

Get budget consumption breakdown

budget_events

Get budget event log

budget_overview

Get project budget overview

completed_yesterday

Get tasks completed yesterday

contributors

Filter by period (week, month, quarter, year). Get contributor activity summary

delete_time_entry

Delete a time tracking entry

get_active_timer

Only one timer can be active at a time. Get the currently running timer

get_task

Use this to verify a task before starting a timer. Get task details by UUID

list_tasks

Filter by status (todo, in-progress, done). List project tasks for time tracking

list_time_entries

List time tracking entries for a project

log_manual_time

Use for retroactive time logging. Create a manual time entry

my_tasks

Ideal for quickly finding what to track time on. Get tasks assigned to me across all workspaces

my_today_tasks

Perfect for daily time tracking workflow. Get tasks due today

productivity_report

Get productivity report

projects_at_risk

Get projects at budget risk

standup_blockers

Get current blockers

standup_summary

Get daily standup summary

start_timer

Only one timer can be active at a time. Use stop_timer to end it. Start a timer on a task

stop_timer

Stop the running timer

stuck_tasks

Get stuck tasks

team_status

Get team member status

team_time_report

Get team time report

time_analytics

Get time tracking analytics

time_reports

Get comprehensive time reports

time_timeline

Get time entries timeline

weekly_digest

Get weekly activity digest

Example Prompts for GitScrum Time Tracking in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with GitScrum Time Tracking immediately.

"Start a timer on task WEB-42 in the web-app project."

"Give me the standup summary for today."

"Which projects are at budget risk?"

Troubleshooting GitScrum Time Tracking MCP Server with VS Code Copilot

Common issues when connecting GitScrum Time Tracking to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

GitScrum Time Tracking + VS Code Copilot FAQ

Common questions about integrating GitScrum Time Tracking MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.