get_all_agile_boardsLABSCO SUMMARY
Both halves of Jira — the issue tracker and the agile board — through one token.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
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
USE CASES
01
Turning a conversation into a ticket
Create the issue with the fields you care about, then attach the file or screenshot that started the discussion.
02
Getting a straight answer about the sprint
List the boards, pick the sprint, read its issues — or run the JQL directly if you already know the query.
03
Moving a ticket without opening the board
Read which transitions that issue actually allows, then apply the one you want and leave a comment explaining it.
04
Tidying an epic before planning
Pull the epics on a board, see what already hangs off one, and move the loose issues under it.
20 tools
Listed in project docs. Your client may show a different list.
get_epics_from_boardget_issues_from_boardget_issues_from_epicget_issues_from_sprintget_sprints_from_boardmove_issues_to_epicadd_jira_commentcreate_issuedelete_issueget_issueget_issue_fieldsget_issue_transitionsget_project_versionssearch_issue_by_jqltransition_jira_issueupdate_issueadd_jira_attachmentssearch_userget_myself_infoBEFORE YOU INSTALL
What to know first
Tools you get
20 tools named in the project's documentation.
Requires
- docker on PATH
- an Atlassian account: your instance URL (atlassian.url), the account email (atlassian.username) and an API token (atlassian.pat) created at id.atlassian.com/manage-profile/security/api-tokens
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"jira": {
"command": "docker",
"args": [
"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"
]
}
}
}docker
TERMINAL
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
