All servers / Project management / Jira MCP server
Jira MCP server
MCP server for Jira Server/Data Center (REST API v2)
Tested by ConnectATDScore 89 out of 100. Tested 2026-11-19 on package version 2.19.0. Package: g-jira-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 19 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (0.8 seconds including download)
- Tools offered: 28
- Last published: 2026-11-17
- Weekly downloads (npm): 1,436
- License: MIT · Direct dependencies: 0
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
get_ticket5 of 5 parameters describedGet full details of a Jira ticket by its key. For a single comment (a ?focusedCommentId= link), use get_comment instead.
transition_ticket2 of 2 parameters describedChange a Jira ticket's status. Matches the transition name or its target status; common aliases (Closed/Resolved -> Done, Reopen -> Re-Open) resolve to whatever the workflow offers. Valid options vary per issue and are listed in the error when no match is found.
transition_tickets2 of 2 parameters describedChange the status of several Jira tickets to the same status, with the same matching as transition_ticket. Tickets are processed in order; a failure on one does not stop the rest, and the result lists each ticket's outcome.
update_ticket14 of 14 parameters describedUpdate fields of a Jira ticket. Changing issue_type to or from a sub-task type, or parent_key of an existing sub-task, goes through Jira's Move/Convert wizards; converting to a sub-task needs parent_key. It stops instead of deleting field values the new type cannot hold, unless allow_field_loss is true.
update_tickets8 of 8 parameters describedApply the same field values (assignee, priority, labels, dates, estimate, epic_key) to several Jira tickets. Tickets are processed in order; a failure on one does not stop the rest, and the result lists each ticket's outcome. Use update_ticket for per ticket text or type changes.
add_comment2 of 2 parameters describedAdd a comment to a Jira ticket
update_comment3 of 3 parameters describedReplace the text of an existing comment on a Jira ticket. Comment IDs are shown by get_ticket with include_comments.
delete_comment2 of 2 parameters describedDelete a comment from a Jira ticket. This cannot be undone. Comment IDs are shown by get_ticket with include_comments.
get_comment3 of 3 parameters describedGet one comment of a Jira ticket by its ID, e.g. from a ?focusedCommentId= link. Cheaper than get_ticket when only that comment matters.
search_tickets2 of 2 parameters describedSearch Jira tickets using JQL query language
create_ticket10 of 10 parameters describedCreate a new Jira ticket
generate_release_notes2 of 2 parameters describedGenerate Markdown release notes for a fix version, grouped by issue type
link_issues3 of 3 parameters describedCreate a link between two Jira tickets
link_tickets3 of 3 parameters describedLink one Jira ticket to several others with the same link type. Links are created in order; a failure on one does not stop the rest, and the result lists each link's outcome.
unlink_issues3 of 3 parameters describedRemove a link between two Jira tickets. Direction does not matter. If several links connect them, pass link_type to pick one.
log_work6 of 6 parameters describedLog work (time) on a Jira ticket, optionally setting WorklogPRO Type of Work and Type of Activity. Check list_worklogs for that day first to avoid a duplicate.
list_worklogs2 of 2 parameters describedList one user's worklogs on one day across all tickets (default: yours), with worklog IDs, WorklogPRO types as [work/activity] ([no type] when unset) and the day's total. Call it before log_work to avoid logging the same work twice.
update_worklog5 of 5 parameters describedEdit a worklog's time, start or comment. Worklog IDs are shown by get_ticket with include_worklogs. To change Type of Work/Activity, delete the worklog and log_work again.
delete_worklog2 of 2 parameters describedDelete a worklog from a Jira ticket. This cannot be undone. Worklog IDs are shown by get_ticket with include_worklogs.
add_watcher2 of 2 parameters describedAdd a user as a watcher of a Jira ticket
add_watchers2 of 2 parameters describedAdd a user as a watcher of several Jira tickets. Tickets are processed in order; a failure on one does not stop the rest, and the result lists each ticket's outcome.
remove_watcher2 of 2 parameters describedRemove a user from the watchers of a Jira ticket
move_to_sprint2 of 2 parameters describedMove Jira tickets into an active or future sprint, by sprint name or ID
list_sprints1 of 1 parameter describedList the active and future sprints of a project's scrum boards, with the IDs move_to_sprint takes
find_user1 of 2 parameters describedFind Jira users by part of a username, display name or email. Returns the username that assignee and watcher fields take
add_attachment2 of 2 parameters describedUpload a local file to a Jira ticket as an attachment. Embed an uploaded image in a comment or description with !filename.png!
delete_attachment1 of 1 parameter describedDelete an attachment from Jira. This cannot be undone. Attachment IDs are shown by get_ticket in the Attachments line.
download_attachment2 of 2 parameters describedDownload a Jira attachment to a local directory, saved under its Jira filename. Attachment IDs are shown by get_ticket in the Attachments line.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.