How to Use the GitScrum Sprints MCP in LlamaIndex

Q: Can LlamaIndex query GitScrum Sprints across all workspaces?

Yes, the agent can call allsprints to retrieve metadata across all workspaces. LlamaIndex then indexes this high-level data so you can search for active sprints across the entire company.

Q: How does LlamaIndex handle rate limits when querying GitScrum Sprints?

You can configure the allowedtools filter to limit which tools like sprintmetrics or listtasks are exposed. This prevents your agent from making too many expensive API calls during RAG indexing.

Q: Can I create new agile items using LlamaIndex?

Yes, your agent can call createuserstory and createsprint to modify your backlog. It uses historical context from your vector store to draft realistic user stories.

Index GitScrum Sprints metrics directly into LlamaIndex vector stores to build semantic search engines for your agile logs.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect GitScrum Sprints MCP to LlamaIndex

Create your Vinkius account to connect GitScrum Sprints to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup GitScrum Sprints with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Index Your GitScrum Sprints Data in LlamaIndex

This MCP server connects `list_tasks` and `list_user_stories` directly to your LlamaIndex data pipelines. The tool outputs are ingested, chunked, and stored in your vector database for immediate semantic querying. Instead of guessing why a previous release slipped, you can query your knowledge base to find relevant blockers. Your agent pulls historical context from `get_sprint` to answer complex questions about team capacity.

Build RAG Pipelines Around Agile Reports

The `sprint_reports` and `sprint_stats` tools feed live performance data into your retrieval-augmented generation loops. Your agent queries the current burndown and burnup charts to ground its answers in real-time project metrics. This setup eliminates hallucinations when discussing project status. By calling `sprint_kpis` dynamically, the agent provides accurate, data-backed updates on team velocity during planning sessions.

Query Backlog Context Dynamically

The `list_epics` and `get_task` tools let your agent search the deep hierarchy of your agile workspace. When a developer asks about a specific feature, the agent fetches the epic structure and active user stories. You configure this MCP server by passing the McpToolSpec to your LlamaIndex FunctionAgent. The agent then decides when to look up a task UUID or list sprints to answer developer questions.

Setup guide

Set up GitScrum Sprints MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all GitScrum Sprints MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to GitScrum Sprints tools.",
)
response = await agent.run("List recent GitScrum Sprints data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by GitScrum. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect GitScrum Sprints now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about GitScrum Sprints MCP in LlamaIndex

Install llama-index-tools-mcp and initialize the BasicMCPClient with your Vinkius URL. Convert the client to tools using McpToolSpec and pass them to your FunctionAgent.

Yes, the agent can call `all_sprints` to retrieve metadata across all workspaces. LlamaIndex then indexes this high-level data so you can search for active sprints across the entire company.

You can configure the allowed_tools filter to limit which tools like `sprint_metrics` or `list_tasks` are exposed. This prevents your agent from making too many expensive API calls during RAG indexing.

Yes, your agent can call `create_user_story` and `create_sprint` to modify your backlog. It uses historical context from your vector store to draft realistic user stories.

Your API tokens are managed entirely by the Vinkius MCP server architecture in an ephemeral sandbox, so your raw credentials never touch LlamaIndex. Only the outputs of tools like `sprint_progress` are sent to your LLM for indexing.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript