What it does
This MCP server integrates Claude with Atlassian Data Center instances of Jira, Confluence, and Bitbucket. It exposes 31 tools for querying and modifying issues, projects, workflows, and related metadata. The server handles credential management through an interactive setup command that validates tokens before persisting them to macOS Keychain, Linux environment files, or Windows user-profile directories.
Who it's for
DevOps engineers and platform teams running Data Center instances who want to automate Jira workflows from Claude. Backend developers integrating issue triage or bulk data operations into AI-assisted processes without authoring custom API clients.
Common use cases
- Query open issues in a project and summarize sprint status
- Programmatically create or update issues based on AI analysis of external data or logs
- Search and filter issues using natural-language constraints
- Transition issues through approval workflows based on analyzed conditions
- Generate aggregated reports from Jira fields
Setup pitfalls
- This server stores 8 secrets including API tokens and host URLs. Keep credential files private; use the interactive
setupcommand to validate tokens before saving. - Non-interactive mode (
--non-interactive) exits with code 1 if credentials cannot be resolved from environment variables, Keychain, or existing config files, rather than prompting interactively. - On macOS, token retrieval shells out to
/usr/bin/securityonce at startup (result is cached); verify Keychain access is permitted and the command is available. - If
ATLASSIAN_DC_MCP_CONFIG_FILEis set, it must be an absolute path; a missing file causes immediate startup failure.