Summary
The Jira reading a team lead does every morning, without opening Jira.
Sprint status, who is overloaded, and yesterday's standup are one call each, assembled from JQL rather than from a dashboard you have to interpret. Issue creation handles the ADF formatting Jira Cloud expects, which is the part that usually fails when you post from a script.
What it is
A Jira server on REST API v3 with five tools aimed at running a team: create and search issues, and generate sprint, workload and standup reports.
What you get
- Issues created with ADF-formatted descriptions, issue type and priority
- JQL search with pagination and formatted results
- Sprint progress reports with metrics and visual indicators
- Workload across named team members, for capacity planning
- A daily standup report: completed, in progress, blocked
- Multiple projects addressed by key, rather than one project fixed at install
- Automatic retry with exponential backoff on rate limits and transient errors
Requirements
Python 3.8 or higher and a Jira Cloud account with an API token. Your Jira site URL, the account's username and that token go in your .env; a default project key and board id can go there too, so most calls need neither.
Setup effort
One command plus a key — uvx mcp-jira, then supply credentials