2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 28 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

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": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "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

Claude Desktop is the definitive way to connect GitScrum Time Tracking to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 28 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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

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

01

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

02

Add the MCP Server

Paste the configuration above into the mcpServers section

03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

04

Start using GitScrum Time Tracking

Look for the 🔌 icon in the chat. your 28 tools are now available

Why Use Claude Desktop with the GitScrum Time Tracking MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with GitScrum Time Tracking through the Model Context Protocol.

01

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

GitScrum Time Tracking + Claude Desktop Use Cases

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

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

GitScrum Time Tracking MCP Tools for Claude Desktop (28)

These 28 tools become available when you connect GitScrum Time Tracking to Claude Desktop 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 Claude Desktop

Ready-to-use prompts you can give your Claude Desktop 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 Claude Desktop

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

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

GitScrum Time Tracking + Claude Desktop FAQ

Common questions about integrating GitScrum Time Tracking MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Connect GitScrum Time Tracking to Claude Desktop

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