Bring Sprint Planning
to CrewAI
Create your Vinkius account to connect GitScrum Sprints to CrewAI and start using all 15 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the GitScrum Sprints MCP Server?
What you can do
- Sprint lifecycle — create, update, delete, and inspect sprints with precise date ranges and configurations
- Performance analytics — access sprint KPIs, detailed statistics, progress tracking, and velocity metrics in real-time
- Visual reports — retrieve burndown, burnup, performance, and distribution chart data for any sprint
- Backlog management — list and create user stories, browse epics, and view tasks filtered by sprint
- Cross-workspace visibility — list sprints across all workspaces for portfolio-level oversight
How it works
- Subscribe to the GitScrum Sprints integration from the marketplace
- Enter your GitScrum API token and company slug
- Ask your agent to review sprint progress, analyze velocity trends, or plan the next iteration — works in Claude, Cursor, and any MCP client
Your agent delivers sprint analytics and agile insights without requiring manual dashboard navigation.
Who is this for?
- Scrum masters — review sprint KPIs and progress during standups and retrospectives
- Engineering managers — track velocity trends and team throughput across sprints
- Product owners — manage user stories and epics while monitoring delivery cadence
Built-in capabilities (15)
List sprints across all workspaces
Create a new sprint
Create a user story
Get sprint details
Get task details by UUID
List epics in a project
List sprints in a project
Use the sprint_slug filter to see only tasks belonging to a specific sprint. Filter by status (todo, in-progress, done). List tasks in a project, optionally filtered by sprint
List user stories in a project
Get sprint KPIs
Get detailed sprint metrics
Get current sprint progress
Resource: burndown, burnup, performance, types, efforts, member_distribution, task, type_distribution. Get sprint reports with charts
Get sprint statistics
Update an existing sprint
Why CrewAI?
When paired with CrewAI, GitScrum Sprints becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call GitScrum Sprints tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
GitScrum Sprints in CrewAI
Why run GitScrum Sprints with Vinkius?
The GitScrum Sprints connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 15 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.
* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.
Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect GitScrum Sprints using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
GitScrum Sprints and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect GitScrum Sprints to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
GitScrum Sprints for CrewAI
Every request between CrewAI and GitScrum Sprints is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
Can my AI agent show me the burndown chart data for the current sprint?
Yes! Use sprint_reports with the resource set to 'burndown'. Your agent returns the ideal versus actual burn-down data points, so you can visualize or analyze sprint health instantly. You can also request 'burnup', 'performance', or 'member_distribution' reports.
Can I see what tasks are in a specific sprint?
Absolutely. Use list_tasks with the sprint_slug filter to see only tasks belonging to that sprint. You can further filter by status (todo, in-progress, done) to focus on what matters. Then use get_task to drill into any specific task for full details.
Does this integration support sprint velocity and metrics tracking?
Yes. Use sprint_metrics for detailed velocity, throughput, and efficiency data. Combined with sprint_kpis for high-level indicators and sprint_stats for task distribution analysis, you get a complete performance picture across any sprint.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Meta Ads
10 toolsEquip your AI agent with direct access to Meta Ads — manage Facebook and Instagram campaigns, track ad performance, and optimize spend without opening Meta Ads Manager.
SEC EDGAR Financials — Revenue, Income, Assets, EPS & Industry Comparison
4 toolsExtract XBRL financial data from SEC filings: revenue, net income, total assets, liabilities, stockholders' equity, EPS, and cash for any U.S. public company. Compare financial metrics across all companies industry-wide using XBRL frames. Like a free mini-Bloomberg terminal.
IQAir
6 toolsMonitor air quality and weather — audit pollution data and cities via AI.
DBeaver (CloudBeaver)
19 toolsManage database connections, users, and server configurations via CloudBeaver's API — inspect drivers, manage teams, and query server status directly.