jira-pm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| setup_projectA | Configure a project for PM Agent monitoring. Validates the root epic, board, fixVersions, and write permissions. Stores config as a YAML comment on the Root Epic. Must be run before any audit tools. |
| list_projects | List all projects registered with the PM Agent, with their configuration summary. |
| list_fix_versions | List all fixVersions (sprints) for a project with dates. Identifies the currently active sprint based on today's date. |
| get_sprint_health | Read-only full sprint health snapshot. Returns the dependency graph: stories → blocking tasks → dates, status, labels, and effective_completion_date per story. Safe to call anytime — makes no changes to JIRA. |
| run_sprint_auditA | Run the daily PM audit for a sprint. Syncs sprint labels on blocking tasks, computes and applies pm-* risk flags, auto-updates story due dates to effective_completion_date, calculates velocity if committed_date is configured, and writes an audit receipt to the Root Epic. Supports dry_run mode. |
| rollback_audit | Reverse the label and story date changes made by a previous run_sprint_audit. Reads the audit receipt from the Root Epic comment and applies the inverse diff. Never removes pm-acknowledged labels. |
| sync_sprint_tasksA | Sync blocking task priorities and sprint labels to match user stories in a sprint. For each story in the sprint, finds all blocking Tasks and: (1) upgrades task priority if lower than the story priority, (2) adds the sprint label if missing. Excludes tasks with "SIT" or "UAT" in their summary. Supports resumable execution via a temp state file. |
| search_issuesA | Escape hatch for ad-hoc JQL queries. Returns a page of matching issues with key, summary, status, assignee, labels, and fixVersions. Use high-level tools (get_sprint_health, run_sprint_audit) for routine PM operations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: setup_project for configuration, run_sprint_audit for comprehensive sprint audit, sync_sprint_tasks for blocking task synchronization, and search_issues as an ad-hoc JQL escape hatch. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case (setup_project, run_sprint_audit, sync_sprint_tasks, search_issues), making the naming predictable and easy to understand.
With 4 tools, the server is well-scoped for its purpose as a PM monitoring assistant. Each tool serves a necessary function (setup, audit, sync, search), and the count fits comfortably within the typical 3-15 range.
The tool set covers the core PM workflow: configuration, audit, task synchronization, and ad-hoc queries. However, it references a 'get_sprint_health' tool that is not provided, and lacks tools for direct issue creation or manual updates, leaving minor gaps.