How to Use the GitScrum Time Tracking MCP in CrewAI

Q: How do multiple agents coordinate GitScrum Time Tracking in CrewAI?

You assign specific MCP tools like starttimer to your Developer Agent and timeanalytics to your Manager Agent. CrewAI's shared memory allows these agents to pass task context back and forth during execution.

Q: Can a CrewAI agent log GitScrum Time Tracking hours retroactively?

Yes, your operations agent can use logmanualtime to record hours after a task is completed. The agent reads completed task lists from your team and logs the precise duration automatically.

Q: How do I limit which GitScrum Time Tracking tools my CrewAI agents can access?

Use CrewAI's toolfilter or MCPServerHTTP to restrict MCP tool access, ensuring your agents only invoke safe read tools like listtasks while blocking destructive actions.

Q: How does CrewAI handle budget alerts?

Your auditor agent can run a continuous loop checking budgetalerts to detect overruns. Once detected, it passes the alert to your communications agent to notify the client.

Deploy specialized agent crews to manage GitScrum task tracking, budget burn-downs, and developer status updates.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect GitScrum Time Tracking MCP to CrewAI

Create your Vinkius account to connect GitScrum Time Tracking to CrewAI 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 Time Tracking with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinate Project Auditing with CrewAI

`budget_consumption` provides the raw financial metrics your budget analyst agent needs to assess team spending over the MCP connection. While that agent calculates burn-downs, a project manager agent coordinates task assignments. The manager agent uses `projects_at_risk` to isolate failing initiatives and reallocate resources. This division of labor keeps your project tracking sharp and responsive.

Run Autonomous Standups with This MCP Server

`standup_summary` gives your standup coordinator agent a structured look at yesterday's progress. A separate QA agent evaluates these summaries to ensure the team is hitting milestone targets. If blockers emerge, the coordinator queries `standup_blockers` to isolate the exact issues. The crew then collaborates to find solutions without interrupting the developers.

Auto-Assign Tasks Based on Real-Time Capacity

`my_today_tasks` retrieves active daily assignments, allowing your resource allocator agent to balance workloads. The agent cross-references these lists to prevent developer burnout. By analyzing `team_time_report`, the allocator agent shifts tasks from overloaded developers to those with open capacity. This ensures your sprints finish on time.

Setup guide

Set up GitScrum Time Tracking MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke GitScrum Time Tracking tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="GitScrum Time Tracking Analyst",
    goal="Access and analyze GitScrum Time Tracking data via MCP.",
    backstory="Expert analyst with direct GitScrum Time Tracking access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent GitScrum Time Tracking transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="GitScrum Time Tracking Analyst",
        goal="Access and analyze GitScrum Time Tracking data via MCP.",
        backstory="Expert analyst with direct GitScrum Time Tracking access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent GitScrum Time Tracking transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

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 Time Tracking 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 Time Tracking MCP in CrewAI

You assign specific MCP tools like `start_timer` to your Developer Agent and `time_analytics` to your Manager Agent. CrewAI's shared memory allows these agents to pass task context back and forth during execution.

Yes, your operations agent can use `log_manual_time` to record hours after a task is completed. The agent reads completed task lists from your team and logs the precise duration automatically.

Use CrewAI's `tool_filter` or `MCPServerHTTP` to restrict MCP tool access, ensuring your agents only invoke safe read tools like `list_tasks` while blocking destructive actions.

Your auditor agent can run a continuous loop checking `budget_alerts` to detect overruns. Once detected, it passes the alert to your communications agent to notify the client.

Your credentials and sprint time reports reside in Vinkius's zero-trust environment, so your CrewAI Python scripts only interact with the secure MCP endpoint. No sensitive API keys are ever stored locally on your agent servers.

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