jira-pm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/panitw/jira-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server