What it does
A Model Context Protocol server that integrates Claude with Jira Cloud for issue management, search, workflow transitions, comments, and attachments. It exposes 6 compound tools covering the full issue lifecycle from creation through status transitions to linking. The compound-tool design reduces token overhead by ~50% compared to 17+ flat tools, leaving more context for actual work.
Who it's for
Engineering teams and project managers using Jira Cloud who want Claude to search, create, and update issues; transition tickets through workflows; manage comments and attachments; and maintain issue relationships without context-switching away from their AI assistant.
Common use cases
- Search issues via JQL and retrieve full details for context
- Create and update issues with custom fields and metadata discovery
- Transition issues through workflow states
- Add and retrieve comments on tickets
- Upload, list, and delete attachments; render images inline
- Create and manage issue links to relate, block, or mark duplicates
Setup pitfalls
- API token must be generated from Atlassian Account Settings (id.atlassian.com), not from within Jira. All three environment variables—
JIRA_EMAIL,JIRA_API_TOKEN,JIRA_BASE_URL—are required. - Requires Node.js 16.0.0 or later.
- Stores Jira credentials in Claude Desktop config as plaintext; rotate API tokens regularly and restrict file access.
- Consider using a service account for shared teams to avoid tying Claude to an individual's account.