Agile Analytics Mcp
mrhenrysword/agile-analytics-mcp
Azure DevOps sprint, cycle time, flow, WIP, aging and forecast metrics. Local, read-only.
- tools
- 6
- auth
- Secret needed
- transport
- STDIO
- env var
- 1
- last updated
- Nov 12, 2026
Tools
6 toolsPublic tool metadata for what this MCP can expose to an agent.
sprint_summaryDelivered items and points, cycle time, carryover, and commitment (committed at the end of day one, completed of committed, reliability, scope added and removed) for a sprint, defaulting to the last finished sprint.
Delivered items and points, cycle time, carryover, and commitment (committed at the end of day one, completed of committed, reliability, scope added and removed) for a sprint, defaulting to the last finished sprint.
No parameter schema in public metadata yet.
cycle_timeCycle time over the last N finished sprints (3, 6 or 12, default 6), never the running one.
Cycle time over the last N finished sprints (3, 6 or 12, default 6), never the running one.
No parameter schema in public metadata yet.
flow_efficiencyFlow efficiency over the last N finished sprints (3, 6 or 12, default 6), never the running one.
Flow efficiency over the last N finished sprints (3, 6 or 12, default 6), never the running one.
No parameter schema in public metadata yet.
wipThe running sprint's items in progress right now.
The running sprint's items in progress right now.
No parameter schema in public metadata yet.
agingOpen work in the current sprint, carried-over items included, with per-item stage, days in that stage and days in flow.
Open work in the current sprint, carried-over items included, with per-item stage, days in that stage and days in flow.
No parameter schema in public metadata yet.
forecastThe Monte Carlo view's default forecast, either how many items in a window (default 30 days) or when a backlog will be done.
The Monte Carlo view's default forecast, either how many items in a window (default 30 days) or when a backlog will be done.
No parameter schema in public metadata yet.
Sponsors
Promote your product hereReach 125k+ visitors monthlyPromote your product hereReach 125k+ visitors monthly
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any language
Agent CaffeineSponsoredClose your lid, come back to finished workSnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthlyWaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthlyknobsSponsoredSee your site on any phone, any day, in any languageConfiguration
AZURE_DEVOPS_PATsecretAzure DevOps personal access token with Work Items: Read, Project and Team: Read and Extension Data: Read. Optional when the Azure CLI is signed in.
Readme
Agile Analytics local AI connector
Ask Claude, or another assistant that supports the Model Context Protocol (MCP), about your team's Agile Analytics numbers: sprint summary, cycle time, flow efficiency, work in progress, aging and forecast. The connector runs on your own computer, reads Azure DevOps with your own access, and answers with the same numbers the Agile Analytics extension shows, because it runs the extension's own metric code.
It is part of your Agile Analytics subscription: it answers only when the extension is installed in your organisation, the organisation is on its trial or has a valid licence, and a workflow mapping is saved for the project. Nothing is sent to Baytek.
Full guide: https://ado-analytics.baytekdev.com/docs/local-ai-connector/
Before you start
Details
- Repository
- github.com/mrhenrysword/agile-analytics-mcp
- Categories
- Cloud & Infrastructure, Monitoring & Observability
- Package
@baytekdev/agile-analytics-mcp- Transport
- STDIO
- Auth
- Required
- Registry
- MCP registry, active
