Wraps JIRA Cloud REST API for AI-driven agile project management, enabling sprint health monitoring, label syncing, risk flagging, and audit receipt writing
Detailed security scan evidence is not public for this MCP yet. Public identity, registry metadata, and independently observed protocol inventory remain available.
Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.
Version 0.1.1 declares 1 executable entrypoint.
npm install --save-exact jira-pm-mcp@0.1.1npx -y -p jira-pm-mcp@0.1.1 jira-pm-mcp{
"mcpServers": {
"jira-pm-mcp": {
"command": "npx",
"args": [
"-y",
"-p",
"jira-pm-mcp@0.1.1",
"jira-pm-mcp"
]
}
}
}| Canonical slug | jira-pm-mcp-fe0b27ab | Deployment | Local Only |
|---|---|---|---|
| Canonical package | npm:jira-pm-mcp | Repository | panitw/jira-mcp-server |
| First published | — | Latest release | — |
| Last security verification | — | Classification confidence | 90% |
| Publication | Draft | Official distribution | Not verified |
| Channel | Identifier | Current version | Versions | Source |
|---|---|---|---|---|
| npm | jira-pm-mcp | 0.1.1 | 1 | Repository |
| Package | Version | Published / observed | Inventory | Security scan |
|---|---|---|---|---|
| npmjira-pm-mcp | 0.1.1Current | Sep 5, 2026 | 8 toolsSucceeded · 0 resources · 0 prompts | Evidence restricted |
Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.
No public current-version evidence is available yet.
| Tool | Category | Annotations | Risk |
|---|---|---|---|
blocker_reportFind and rank everything getting in the way in a sprint. Goes beyond the Blocked column: fuses the impediment flag, open 'is blocked by' links, hard Blocked status, stale in-progress tickets, and natural-language cues in comments ('waiting on', 'stuck', 'dependency') into one severity-ranked list. Defaults to the active sprint.Input schema{
"type": "object",
"properties": {
"boardId": {
"type": "integer",
"description": "Board id. Optional when the account has a single board. Use jira_list_boards to find ids."
},
"sprintId": {
"type": "integer",
"description": "Sprint id. Optional: defaults to the active sprint (or the most recent closed one)."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
burndown_analysisReconstruct the sprint burndown from the changelog: remaining work per day vs the ideal line, daily burn rate vs the rate needed to finish, and a projected completion date. This is a close approximation built from issue history, not a copy of Jira's chart. Defaults to the active sprint.Input schema{
"type": "object",
"properties": {
"boardId": {
"type": "integer",
"description": "Board id. Optional when the account has a single board. Use jira_list_boards to find ids."
},
"sprintId": {
"type": "integer",
"description": "Sprint id. Optional: defaults to the active sprint (or the most recent closed one)."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
jira_list_boardsList the Jira boards this account can see, with their ids. Use the id with the other tools when the account has more than one board.Input schema{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {}
} | — | — | |
jira_list_sprintsList sprints for a board with their ids, state, and dates. Pass a boardId when the account has multiple boards. Optionally filter by state.Input schema{
"type": "object",
"properties": {
"boardId": {
"type": "integer",
"description": "Board id. Optional when the account has a single board."
},
"state": {
"type": "string",
"enum": [
"active",
"closed",
"future"
],
"description": "Filter by sprint state."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
sprint_health_summaryRead of how a sprint is tracking: completion vs time elapsed, a plain-language verdict (on track / at risk / behind), scope added mid-sprint, and the specific items putting the sprint at risk (blocked, stale, unassigned). Defaults to the active sprint. Falls back to issue counts when the team does not estimate in points.Input schema{
"type": "object",
"properties": {
"boardId": {
"type": "integer",
"description": "Board id. Optional when the account has a single board. Use jira_list_boards to find ids."
},
"sprintId": {
"type": "integer",
"description": "Sprint id. Optional: defaults to the active sprint (or the most recent closed one)."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
standup_generatorGenerate a daily standup, grouped by assignee: what each person finished recently, what they are working on, and what is blocking them. Pasteable straight into Slack. Defaults to the active sprint and a one-day lookback (use sinceDays for Monday standups that cover the weekend).Input schema{
"type": "object",
"properties": {
"boardId": {
"type": "integer",
"description": "Board id. Optional when the account has a single board. Use jira_list_boards to find ids."
},
"sprintId": {
"type": "integer",
"description": "Sprint id. Optional: defaults to the active sprint (or the most recent closed one)."
},
"sinceDays": {
"type": "integer",
"minimum": 1,
"maximum": 14,
"description": "Lookback window in days for 'recently done'. Default 1."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
velocity_trendsVelocity across recent closed sprints: committed vs completed per sprint, average velocity, commitment accuracy, predictability (how consistent the team is), the trend, and a recommended commitment for the next sprint. Pass a boardId if the account has more than one board.Input schema{
"type": "object",
"properties": {
"boardId": {
"type": "integer",
"description": "Board id. Optional when the account has a single board."
},
"count": {
"type": "integer",
"minimum": 2,
"maximum": 20,
"description": "How many recent closed sprints to analyze. Default 5."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
weekly_status_noteGenerate a stakeholder-ready weekly status note: a single RAG status, a short narrative, what was delivered this week, the top risks and blockers with owners, velocity context, and the focus for next week. Composes sprint health, blockers, and velocity into one note you can send as-is. Defaults to the active sprint.Input schema{
"type": "object",
"properties": {
"boardId": {
"type": "integer",
"description": "Board id. Optional when the account has a single board. Use jira_list_boards to find ids."
},
"sprintId": {
"type": "integer",
"description": "Sprint id. Optional: defaults to the active sprint (or the most recent closed one)."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — |
| Endpoint | Transport | Authentication | Health | Observed |
|---|---|---|---|---|
| No verified remote endpoint is linked. | ||||
Install the selected package version with: npm install --save-exact jira-pm-mcp@0.1.1
jira-pm-mcp Server exposed 8 tools during independent protocol observation, including blocker_report, burndown_analysis, jira_list_boards, jira_list_sprints, sprint_health_summary, standup_generator, velocity_trends, weekly_status_note.
The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.
These internal links are derived from strong identity fields such as the implementation name, package, repository, vendor, and listing name—not generic description prose.
Association is based on retained identity fields; it does not by itself prove first-party publication.
Curated product and capability guides containing this catalog record.