An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Gitscrum Time Tracking to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Manage your team's time and budgets through natural conversation.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 28 capabilities

We ship only the actions that matter.

Capability set01 / 07

01-04

4 capabilities in this set.

Part of 28 available through GitScrum.

  1. 01

    Budget alerts

    This capability fetches alerts when your project hits specific budget thresholds.

  2. 02

    Budget burndown

    Get the data needed to visualize how quickly your project budget is being consumed.

  3. 03

    Budget events

    Access a log of all events related to your project budget.

  4. 04

    Budget overview

    Get a high-level summary of your current project budget status.

Capability set02 / 07

05-08

4 capabilities in this set.

Part of 28 available through GitScrum.

  1. 05

    Projects at risk

    Identify which projects are currently exceeding or approaching their budget limits.

  2. 06

    Standup blockers

    Retrieve a list of current blockers that are stalling progress.

  3. 07

    Stuck tasks

    Find tasks that have been stuck or inactive for too long.

  4. 08

    Standup summary

    Get an automated summary of your daily standup details.

Capability set03 / 07

09-12

4 capabilities in this set.

Part of 28 available through GitScrum.

  1. 09

    Team status

    Check the current status of individual team members.

  2. 10

    My today tasks

    List the specific tasks assigned to you that are due today.

  3. 11

    List time entries

    Retrieve all time tracking entries recorded for a specific project.

  4. 12

    Time analytics

    Access analytical data regarding how time is being tracked and spent.

Capability set04 / 07

13-16

4 capabilities in this set.

Part of 28 available through GitScrum.

  1. 13

    Productivity report

    Generate a report detailing team or individual productivity levels.

  2. 14

    Time reports

    Get detailed time tracking reports for your projects.

  3. 15

    Team time report

    Pull a report specifically focused on time spent by the team.

  4. 16

    Time timeline

    View a chronological timeline of all recorded time entries.

Capability set05 / 07

17-20

4 capabilities in this set.

Part of 28 available through GitScrum.

  1. 17

    Budget consumption

    Get a detailed breakdown of how the budget is being used.

  2. 18

    Completed yesterday

    See a list of all tasks that were finished yesterday.

  3. 19

    Contributors

    Get a summary of activity for contributors over a specific period.

  4. 20

    Delete time entry

    Remove a specific time tracking entry from the system.

Capability set06 / 07

21-24

4 capabilities in this set.

Part of 28 available through GitScrum.

  1. 21

    Get active timer

    Check which timer is currently running.

  2. 22

    Get task

    Retrieve specific details for a task using its UUID.

  3. 23

    List tasks

    List project tasks filtered by their current status.

  4. 24

    Log manual time

    Create a manual time entry for work that was already completed.

Capability set07 / 07

25-28

4 capabilities in this set.

Part of 28 available through GitScrum.

  1. 25

    My tasks

    Find all tasks assigned to you across all available workspaces.

  2. 26

    Start timer

    Begin tracking time on a specific task.

  3. 27

    Stop timer

    End the currently active timer.

  4. 28

    Weekly digest

    Get a summary of all activity from the past week.

Real work

What teams actually run

01

Hands-free Coding

A developer starts a timer on a task via the chat interface before beginning a new feature.

02

Daily Syncs

A team lead asks for a standup summary to see what was finished yesterday and what is currently stuck.

03

Budget Audits

A project manager checks the budget burn-down to see if a project will exceed its limit this month.

04

Performance Reviews

A manager pulls a weekly digest to review contributor activity and time distribution.

Automate a task

Put GitScrum to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

GitScrum works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put GitScrum to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1161ms average. Fast in production.

GitScrum is checked daily against the live service.

Daily averagePeak 1378ms
Oct 3Today
Fastest day
859ms
Slowest day
1378ms
14-day trend
Improving-5%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 28 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of GitScrum, so you can see the experience inside your AI.

It does not authenticate your account with GitScrum. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

GitScrum Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_2iGgDQUCIaLPRgPaZwgFAGAHENxVPaHPC9D81h7y/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — GitScrum capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "gitscrum-time-tracking-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_2iGgDQUCIaLPRgPaZwgFAGAHENxVPaHPC9D81h7y/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up GitScrum in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work GitScrum owners hand off.

This MCP is built for technical teams and project leaders who want to manage workflows without leaving their primary workspace.

  • 01

    Developers

    They use the agent to start and stop timers directly from their IDE.

  • 02

    Team Leads

    They use the agent to quickly review standup summaries and identify blockers.

  • 03

    Project Managers

    They use the agent to monitor budget health and track billable hours.

FAQ

Questions GitScrum owners ask.

  • 01

    How do I use this MCP with my IDE?

    Once you connect the MCP to a compatible client like Cursor or VS Code, you can use the capabilities through your existing chat or command interface.

  • 02

    Can I log time for work I did yesterday?

    Yes, you can use the manual time logging capability to create retroactive entries with specific timestamps.

  • 03

    Does this MCP support multiple projects?

    Yes, you can query tasks, time entries, and budget data for specific projects using their names or IDs.

  • 04

    How does the budget monitoring work?

    The agent can access budget overview, consumption breakdowns, and alerts to tell you exactly how much of your budget remains.

  • 05

    What happens if I have two timers running?

    The system only allows one active timer at a time. You must stop the current timer before starting a new one.

  • 06

    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.

  • 07

    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.

  • 08

    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.

Explore

More in Productivity

Suggestions

Connect GitScrum to Claude, Cursor, ChatGPT & more