2,500+ MCP servers ready to use
Vinkius

GitScrum Time Tracking MCP Server for Cursor 28 tools — connect in under 2 minutes

Built by Vinkius GDPR 28 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "gitscrum-time-tracking": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
GitScrum Time Tracking
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

Cursor's Agent mode turns GitScrum Time Tracking into an in-editor superpower. Ask Cursor to generate code using live data from GitScrum Time Tracking and it fetches, processes, and writes. all in a single agentic loop. 28 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

The GitScrum Time Tracking MCP Server exposes 28 tools through the Vinkius. Connect it to Cursor 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 Cursor via MCP

Follow these steps to integrate the GitScrum Time Tracking MCP Server with Cursor.

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

03

Save the file

Cursor will automatically detect the new MCP server

04

Start using GitScrum Time Tracking

Open Agent mode in chat and ask: "Using GitScrum Time Tracking, help me...". 28 tools available

Why Use Cursor with the GitScrum Time Tracking MCP Server

Cursor AI Code Editor provides unique advantages when paired with GitScrum Time Tracking through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

GitScrum Time Tracking + Cursor Use Cases

Practical scenarios where Cursor combined with the GitScrum Time Tracking MCP Server delivers measurable value.

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

GitScrum Time Tracking MCP Tools for Cursor (28)

These 28 tools become available when you connect GitScrum Time Tracking to Cursor via MCP:

01

budget_alerts

Get budget threshold alerts

02

budget_burndown

Get budget burn-down chart data

03

budget_consumption

Get budget consumption breakdown

04

budget_events

Get budget event log

05

budget_overview

Get project budget overview

06

completed_yesterday

Get tasks completed yesterday

07

contributors

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

08

delete_time_entry

Delete a time tracking entry

09

get_active_timer

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

10

get_task

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

11

list_tasks

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

12

list_time_entries

List time tracking entries for a project

13

log_manual_time

Use for retroactive time logging. Create a manual time entry

14

my_tasks

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

15

my_today_tasks

Perfect for daily time tracking workflow. Get tasks due today

16

productivity_report

Get productivity report

17

projects_at_risk

Get projects at budget risk

18

standup_blockers

Get current blockers

19

standup_summary

Get daily standup summary

20

start_timer

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

21

stop_timer

Stop the running timer

22

stuck_tasks

Get stuck tasks

23

team_status

Get team member status

24

team_time_report

Get team time report

25

time_analytics

Get time tracking analytics

26

time_reports

Get comprehensive time reports

27

time_timeline

Get time entries timeline

28

weekly_digest

Get weekly activity digest

Example Prompts for GitScrum Time Tracking in Cursor

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

01

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

02

"Give me the standup summary for today."

03

"Which projects are at budget risk?"

Troubleshooting GitScrum Time Tracking MCP Server with Cursor

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

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

GitScrum Time Tracking + Cursor FAQ

Common questions about integrating GitScrum Time Tracking MCP Server with Cursor.

01

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
02

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
03

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
04

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Connect GitScrum Time Tracking to Cursor

Get your token, paste the configuration, and start using 28 tools in under 2 minutes. No API key management needed.