Jira Data Center MCP Server by b1ff: Search and Edit Issues with AI

• Finds issues with a JQL query

  Runs a JQL search against your Jira Data Center and returns matching issues. You can limit the fields, expand sections and page through results.

  Try: “Find open bugs assigned to me in project PAY”

  Network · jira_searchIssues

• Shows one issue in full

  Fetches an issue by key, with its fields, subtasks and parent. You can ask for extra sections such as changelog or rendered fields.

  Try: “Show me PAY-123 with its changelog”

  Network · jira_getIssue

• Lists the comments on an issue

  Returns the comments on an issue by key, paged, with an option for rendered text.

  Try: “Show the comments on PAY-123”

  Network · jira_getIssueComments

• Creates a new issue

  Makes an issue in a project from a summary, a wiki-markup description and an issue type ID. Custom fields and labels go in an extra object.

  Try: “Create a bug in PAY titled "Refund fails on retry"”

  Write · jira_createIssue

• Edits an issue's fields

  Changes the summary, description, issue type or custom fields of an existing issue. Fields you leave out stay as they are.

  Try: “Change the summary of PAY-123 to "Refund fails after retry"”

  Write · jira_updateIssue

• Adds a comment to an issue

  Posts a new comment, written in Jira wiki markup, on the issue you name.

  Try: “Comment on PAY-123 that the fix is in review”

  Write · jira_postIssueComment

• Rewrites an existing comment

  Replaces the text of a comment you point to by ID. Look the ID up with the comments tool first.

  Try: “Fix the typo in my last comment on PAY-123”

  Write · jira_updateIssueComment

• Lists the status moves an issue allows

  Returns the workflow transitions available for an issue, with their IDs, names and target statuses.

  Try: “What status can PAY-123 move to?”

  Network · jira_getTransitions

• Moves an issue to another status

  Applies a workflow transition by ID, such as In Progress to Done. Get the allowed IDs from the transitions tool first.

  Try: “Move PAY-123 to Done”

  Write · jira_transitionIssue

• Shows linked pull requests, commits or branches

  Reads the Development panel of an issue and returns linked pull requests by default, from Bitbucket unless you name another application. You can ask for commits or branches instead.

  Try: “Which pull requests are linked to PAY-123?”

  Network · jira_getIssueDevelopmentInfo

• Lists the issue link types

  Returns the link types your Jira knows, such as Blocks, Relates and Duplicate, so you can use a valid name when linking.

  Try: “What link types does our Jira have?”

  Network · jira_getIssueLinkTypes

• Links two issues together

  Creates a link of a chosen type between two issues. The tool warns that direction is easy to get backwards, so it asks the assistant to read the first issue afterwards and check.

  Try: “Mark PAY-123 as blocking PAY-130”

  Write · jira_linkIssues

• Removes a link between two issues

  Deletes an existing issue link by its link ID, which you find in the issue's links field.

  Try: “Remove the link between PAY-123 and PAY-130”

  Delete · jira_unlinkIssues

• Adds you as a watcher

  Adds the signed-in user as a watcher on an issue. It cannot add anyone else.

  Try: “Watch PAY-123 for me”

  Write · jira_watchIssue

• Removes you as a watcher

  Takes the signed-in user off the watcher list of an issue. It cannot change anyone else's watching.

  Try: “Stop watching PAY-123”

  Write · jira_unwatchIssue

• Lists a project's versions

  Returns the versions (releases) of a project with IDs, names, dates and release state. You can filter by name, released and archived state.

  Try: “List unreleased versions of project PAY”

  Network · jira_getProjectVersions

• Shows one version

  Fetches a project version by ID. To see its issues, the tool points the assistant to a JQL search on fixVersion.

  Try: “Show version 10200”

  Network · jira_getVersion

• Creates a project version

  Adds a new version (release) to a project, with optional description and dates. It suggests checking the existing list first to avoid duplicate names.

  Try: “Create version 2.4.0 in project PAY”

  Write · jira_createVersion

• Edits, releases or archives a version

  Renames a version, changes its description or dates, marks it released or archives it. Only the fields you give are changed.

  Try: “Release version 2.4.0 today”

  Write · jira_updateVersion

• Reads attachments from an issue

  Lists an issue's attachments, or returns the contents of one as text, base64 or a viewable image. Files over 1 MiB come back as metadata unless you raise the limit. It saves nothing to disk unless the operator turns that on.

  Try: “Show the screenshot attached to PAY-123”

  Network · jira_downloadAttachment

Watch out for

• It can delete issue links

  The unlink tool removes a link between two issues and is on by default. Everything it does uses your token's permissions, so use an account with limited project access. npmjs.com

• It creates and edits issues and comments

  The assistant can create issues, rewrite descriptions and comments, change statuses and release or archive versions. There is no read-only switch, so a token with read-only Jira permissions is the only way to prevent writes. github.com

• Opt-in setting can delete project versions

  Setting JIRA_VERSION_DELETE_ENABLED to true registers a tool that deletes a version and strips it from every issue that uses it. Leave it off unless you need it. github.com

• Attachment upload and saving are off by default

  Turning on the attachment settings lets the assistant read files from, and save files into, folders you name. Use a dedicated folder, as the README advises. github.com

• Attachments are untrusted content

  Downloaded attachment text or images can contain instructions aimed at the assistant. The tool itself tells the assistant to treat them as data. npmjs.com

Security advisories