Boards, sprints and epics come from the Software API and issues from the Platform API; most Jira connectors cover only the first half. Transitions are two calls on purpose: read the legal moves for that issue, then make one, rather than guessing a status name.
A Java server that covers both the Jira Platform REST API and the Jira Software API, so issues and the agile side (boards, sprints, epics) are reachable through the same connection.
- get_all_agile_boards, get_sprints_from_board, get_issues_from_board, get_epics_from_board
- get_issues_from_epic, get_issues_from_sprint, move_issues_to_epic
- create_issue, get_issue, update_issue, delete_issue
- search_issue_by_jql — any JQL query you can write
- get_issue_transitions and transition_jira_issue — see the legal status moves, then make one
- add_jira_comment and add_jira_attachments
- get_issue_fields and get_project_versions, with pagination
- search_user and get_myself_info
Your Atlassian instance URL, your account email and an Atlassian API token, passed as atlassian.url, atlassian.username and atlassian.pat. Ships as a Docker image serving MCP over SSE on port 8080; stdio mode needs quarkus.mcp.server.stdio.enabled=true and the console logging switched off.
One command plus a key — docker run --rm -e atlassian.url=https://your-company.atlassian.net -e atlassian.username=your-jira-email -e atlassian.pat=your-jira-pat -e quarkus.mcp.server.stdio.enabled=true -e quarkus.log.console.enable=false -e quarkus.log.console.stderr=false -i guang1/jira-mcp:latest, then supply credentials