What problem does it solve? Working with on-prem Atlassian Jira and Confluence through an MCP server requires correct instance routing, workflow-safe transitions, and base64 attachment handling, which agents often get wrong by assuming Atlassian Cloud behavior. ## Core Features & Use Cases - Jira Issue Operations: Search with JQL, create, update, comment on, transition, and link issues across EMEA and global Jira instances with automatic project-key routing. - Confluence Page Management: Search, read, create, update, label, and attach files to Confluence pages using storage-format content. - Attachments and Linking: Upload and download Jira and Confluence attachments via base64 payloads and create Jira remote links to Confluence pages. - Use Case: A user asks to move issue OPS-123 to "Reviewed" and attach a generated report; the skill first lists available transitions, then performs the transition and uploads the base64-encoded file to the correct Jira instance. ## Quick Start Ask the agent to search Jira for open issues in your project and transition one of them to the next workflow state using the on-prem Atlassian MCP.