GitScrum Time Tracking MCP Server for LlamaIndex 28 tools — connect in under 2 minutes
LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add GitScrum Time Tracking as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI
async def main():
# Your Vinkius token. get it at cloud.vinkius.com
mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
mcp_tool_spec = McpToolSpec(client=mcp_client)
tools = await mcp_tool_spec.to_tool_list_async()
agent = FunctionAgent(
tools=tools,
llm=OpenAI(model="gpt-4o"),
system_prompt=(
"You are an assistant with access to GitScrum Time Tracking. "
"You have 28 tools available."
),
)
response = await agent.run(
"What tools are available in GitScrum Time Tracking?"
)
print(response)
asyncio.run(main())
* 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
LlamaIndex agents combine GitScrum Time Tracking tool responses with indexed documents for comprehensive, grounded answers. Connect 28 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
The GitScrum Time Tracking MCP Server exposes 28 tools through the Vinkius. Connect it to LlamaIndex 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 LlamaIndex via MCP
Follow these steps to integrate the GitScrum Time Tracking MCP Server with LlamaIndex.
Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token
Run the agent
Save to agent.py and run: python agent.py
Explore tools
The agent discovers 28 tools from GitScrum Time Tracking
Why Use LlamaIndex with the GitScrum Time Tracking MCP Server
LlamaIndex provides unique advantages when paired with GitScrum Time Tracking through the Model Context Protocol.
Data-first architecture: LlamaIndex agents combine GitScrum Time Tracking tool responses with indexed documents for comprehensive, grounded answers
Query pipeline framework lets you chain GitScrum Time Tracking tool calls with transformations, filters, and re-rankers in a typed pipeline
Multi-source reasoning: agents can query GitScrum Time Tracking, a vector store, and a SQL database in a single turn and synthesize results
Observability integrations show exactly what GitScrum Time Tracking tools were called, what data was returned, and how it influenced the final answer
GitScrum Time Tracking + LlamaIndex Use Cases
Practical scenarios where LlamaIndex combined with the GitScrum Time Tracking MCP Server delivers measurable value.
Hybrid search: combine GitScrum Time Tracking real-time data with embedded document indexes for answers that are both current and comprehensive
Data enrichment: query GitScrum Time Tracking to augment indexed data with live information before generating user-facing responses
Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying GitScrum Time Tracking for fresh data
Analytical workflows: chain GitScrum Time Tracking queries with LlamaIndex's data connectors to build multi-source analytical reports
GitScrum Time Tracking MCP Tools for LlamaIndex (28)
These 28 tools become available when you connect GitScrum Time Tracking to LlamaIndex 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 LlamaIndex
Ready-to-use prompts you can give your LlamaIndex 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 LlamaIndex
Common issues when connecting GitScrum Time Tracking to LlamaIndex through the Vinkius, and how to resolve them.
BasicMCPClient not found
pip install llama-index-tools-mcpGitScrum Time Tracking + LlamaIndex FAQ
Common questions about integrating GitScrum Time Tracking MCP Server with LlamaIndex.
How does LlamaIndex connect to MCP servers?
Can I combine MCP tools with vector stores?
Does LlamaIndex support async MCP calls?
Connect GitScrum Time Tracking with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect GitScrum Time Tracking to LlamaIndex
Get your token, paste the configuration, and start using 28 tools in under 2 minutes. No API key management needed.