Skip to content
Agentmart
Submit a tool

Atlassian Dc MCP Jira

MCP server for Atlassian Jira Data Center - search, view, and create issues

Connector by b1ff · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 105
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/b1ff-atlassian-dc-mcp-jira

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

MCP server for Atlassian Jira Data Center - search, view, and create issues

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools
29 read · 21 write · 2 delete · 1 not yet classified
Secrets
1 (API keys, tokens or passwords)
Install scripts
None found
Runs as
Node.js package

Tools by what they do 53

Read from the source code; the running server may list different tools.

Read 29 · Look things up without changing anything.

  • bitbucket_browseRepository
  • bitbucket_canMergePullRequest
  • bitbucket_getBranchDiff
  • bitbucket_getCommits
  • bitbucket_getDashboardPullRequests
  • bitbucket_getFileContent
  • bitbucket_getInboxPullRequests
  • bitbucket_getPR_CommentsAndAction
  • bitbucket_getProject
  • bitbucket_getProjects
  • bitbucket_getPullRequest
  • bitbucket_getPullRequestBuilds
Show 17 more tools
  • bitbucket_getPullRequestChanges
  • bitbucket_getPullRequestDiff
  • bitbucket_getPullRequests
  • bitbucket_getRepositories
  • bitbucket_getRepository
  • bitbucket_getRequiredReviewers
  • bitbucket_getUser
  • bitbucket_searchCode
  • confluence_getContent
  • confluence_searchContent
  • confluence_searchSpace
  • jira_getIssue
  • jira_getIssueComments
  • jira_getIssueDevelopmentInfo
  • jira_getIssueLinkTypes
  • jira_getTransitions
  • jira_searchIssues

Write 21 · Create, change, send or run things.

  • bitbucket_createBranch
  • bitbucket_createPullRequest
  • bitbucket_declinePullRequest
  • bitbucket_mergePullRequest
  • bitbucket_postPullRequestComment
  • bitbucket_reopenPullRequest
  • bitbucket_submitPullRequestReview
  • bitbucket_updatePullRequest
  • bitbucket_updatePullRequestComment
  • confluence_createContent
  • confluence_downloadAttachment
  • confluence_updateContent
Show 9 more tools
  • confluence_uploadAttachment
  • jira_createIssue
  • jira_downloadAttachment
  • jira_linkIssues
  • jira_postIssueComment
  • jira_transitionIssue
  • jira_updateIssue
  • jira_updateIssueComment
  • jira_uploadAttachment

Delete 2 · Delete, drop, revoke or wipe things.

  • jira_unlinkIssues
  • jira_unwatchIssue

Not yet classified 1 · We could not tell from the name and description.

  • jira_watchIssue

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • JIRA_API_TOKEN

Other settings (environment variables or headers).

  • ATLASSIAN_DC_MCP_CONFIG_FILE
  • JIRA_API_BASE_PATH
  • JIRA_HOST

Network hosts it talks to 1

  • github.com · found in code

Files it touches

  • /dev/null
  • Your home directory (~)
  • Any path the agent passes to its tools

Tools (53)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • bitbucket_browseRepositoryread-only

    Browse a Bitbucket repository at a branch, tag or commit using structured, paginated responses. Omit 'path' to list the repository root. Directory pagination is under 'children'; file pagination is at the response root. Continue with the corresponding 'nextPageStart' when 'isLastPage' is false. For a complete raw file or compact unpaginated git tree listing, use bitbucket_getFileContent.

  • bitbucket_canMergePullRequestread-only

    Check whether a pull request can be merged. Read-only: returns canMerge, whether the pull request is conflicted, and any merge-check vetoes (e.g. missing approvals, unresolved tasks, failed builds). Use this before bitbucket_mergePullRequest to see what is blocking a merge.

  • bitbucket_createBranch

    Create a branch in a Bitbucket repository, forked from a branch, tag or commit. Use this before bitbucket_createPullRequest when the source branch does not exist yet. The response contains the new branch's 'id' (e.g. 'refs/heads/feature/my-branch'), which is what bitbucket_createPullRequest expects as fromRefId.

  • bitbucket_createPullRequest

    Create a new pull request in a Bitbucket repository. Supports fork-based pull requests by passing fromProjectKey/fromRepositorySlug when the source repository differs from the destination (projectKey/repositorySlug). IMPORTANT: Before creating a PR, use bitbucket_getRequiredReviewers to fetch required reviewers for the source and target branches to ensure the PR is not created without mandatory reviewers.

  • bitbucket_declinePullRequest

    Description is built at runtime.

  • bitbucket_getBranchDiffread-only

    Get the diff between two branches, tags or commits — including branches that have no pull request yet. Returns the same comparison as the Bitbucket 'compare' view: changes reachable from sourceBranch but not from targetBranch, rendered as a unified diff. targetBranch defaults to the repository's default branch. Use this to review work in progress before a PR exists; once a PR exists, prefer bitbucket_getPullRequestChanges + bitbucket_getPullRequestDiff.

  • bitbucket_getCommitsread-only

    Get commits for a Bitbucket repository

  • bitbucket_getDashboardPullRequestsread-only

    Get pull requests from the Bitbucket dashboard across all repositories. Useful for finding all PRs where you are the author, reviewer, or participant without specifying a project or repository.

  • bitbucket_getFileContentread-only

    Get the raw content of a file in a Bitbucket repository, at a branch, tag or commit. Use this to read a complete source file without cloning the repository. 'at' defaults to the repository's default branch. Pointing 'path' at a directory returns that directory's unpaginated git tree listing. For structured, paginated directory listings or file reads, use bitbucket_browseRepository.

  • bitbucket_getInboxPullRequestsread-only

    Get pull requests from the authenticated user's inbox that need their review. Returns PRs across all repositories where the user is a reviewer.

  • bitbucket_getPR_CommentsAndActionread-only

    Get comments for a Bitbucket pull request and other actions, like approvals

  • bitbucket_getProjectread-only

    Get a specific Bitbucket project by key

  • bitbucket_getProjectsread-only

    Get a list of Bitbucket projects

  • bitbucket_getPullRequestread-only

    Get a specific pull request by ID. Returns full details including title, description, reviewers, participants, author, source/target branches, current state, and version (needed for bitbucket_updatePullRequest).

  • bitbucket_getPullRequestBuildsread-only

    Get the CI/CD build statuses of a pull request — the builds, jobs or pipelines that any CI server integrated with Bitbucket (Jenkins, Bamboo, TeamCity or any other tool posting build statuses) reported on the latest commit of its source branch, as shown in the pull request's Builds panel. Use it to check whether a pull request's checks passed, failed or are still running, e.g. after a push. Read-only. Returns the commit id, counts per state, and for each build its state (SUCCESSFUL, FAILED, INPROGRESS, CANCELLED, UNKNOWN), name, url of the run in the CI server and description.

Show 38 more tools
  • bitbucket_getPullRequestChangesread-only

    Get the changes for a Bitbucket pull request

  • bitbucket_getPullRequestDiffread-only

    Get text diff for a specific file in a Bitbucket pull request. Returns plain text diff format. Note: Before getting diff, use getPullRequestChanges to understand what files were changed in the PR

  • bitbucket_getPullRequestsread-only

    Get pull requests for a Bitbucket repository

  • bitbucket_getRepositoriesread-only

    Get repositories for a Bitbucket project

  • bitbucket_getRepositoryread-only

    Get a specific Bitbucket repository

  • bitbucket_getRequiredReviewersread-only

    Get required reviewers for pull request creation. Returns a set of users who are required reviewers for pull requests created from the given source repository and ref to the given target ref in this repository.

  • bitbucket_getUserread-only

    Get a Bitbucket user by their slug, or search for users by name/email to discover their slug. Use this to resolve userSlug for bitbucket_submitPullRequestReview when it is not already known from a comment response or PR participant list.

  • bitbucket_mergePullRequest

    Description is built at runtime.

  • bitbucket_postPullRequestComment

    Post a comment to a Bitbucket pull request. Use pending: true to create a draft comment that is only visible to you until you call bitbucket_submitPullRequestReview. NOTE: pending only works when filePath is provided (file-level or inline comments). True top-level PR comments (no filePath) are always posted live and cannot be drafted. Use severity: 'BLOCKER' to post the comment as a task — tasks must be resolved before the PR can be merged.

  • bitbucket_reopenPullRequest

    Reopen a declined pull request, restoring it to OPEN. IMPORTANT: you MUST first call bitbucket_getPullRequest to get the current 'version' — it is required for optimistic locking and a stale version is rejected. The pull request must be in the DECLINED state; anything else is refused.

  • bitbucket_searchCoderead-only

    Search code across Bitbucket. The query supports search modifiers like 'project:<key>', 'repo:<key>/<slug>', and 'ext:<extension>' to scope or filter results (e.g. 'project:TEST authenticate', 'repo:TEST/demo ext:js TODO'). NOTE: the 'repo:' modifier requires the project key — 'repo:projectkey/repositoryslug', not a bare slug. Returns matching files with hit contexts (snippets).

  • bitbucket_submitPullRequestReview

    Submit a pull request review, publishing all pending (draft) comments and setting the reviewer's verdict. This is equivalent to clicking 'Submit Review' in the Bitbucket UI. Use after posting comments with pending: true. To resolve userSlug: (1) check author.slug in any comment you posted this session, (2) check the reviewers/participants array from bitbucket_getPullRequest, or (3) call bitbucket_getUser with a name/email filter as a last resort.

  • bitbucket_updatePullRequest

    Update the title, description, reviewers, destination branch or draft status of an existing pull request. IMPORTANT: You MUST first call bitbucket_getPullRequest to get the current 'version' number — this is required for optimistic locking and the call will fail without it. Omit reviewers to keep the current ones. When passed, reviewers replaces ALL existing reviewers: to add someone, include the current reviewers from the PR details along with the new ones.

  • bitbucket_updatePullRequestComment

    Update an existing pull request comment. Use to edit text, change severity, change task state, or resolve/reopen the comment thread. On a BLOCKER (task) comment, state: 'RESOLVED' ticks the task; threadResolved: true toggles the thread-level 'Resolve' button. These are independent and can be set separately. Requires the current 'version' from optimistic locking; fetch it via bitbucket_getPR_CommentsAndAction or use the version returned when the comment was created.

  • confluence_createContent

    Create new content in Confluence Data Center edition instance

  • confluence_downloadAttachment

    Description is built at runtime.

  • confluence_getContentread-only

    Get Confluence content by ID from the Confluence Data Center edition instance

  • confluence_searchContentread-only

    Search for content in Confluence Data Center edition instance using CQL

  • confluence_searchSpaceread-only

    Search for spaces in Confluence Data Center edition instance

  • confluence_updateContent

    Update existing content in Confluence Data Center edition instance. Optionally move the page by setting parentId.

  • confluence_uploadAttachment

    Upload a local file as an attachment to a Confluence content (page) in the Confluence Data Center edition instance. The file must live under the server-configured upload directory; the path is given relative to that directory.

  • jira_createIssue

    Create a new JIRA issue in the JIRA Data Center edition instance

  • jira_downloadAttachment

    Description is built at runtime.

  • jira_getIssueread-only

    Get details of a JIRA issue by its key from the JIRA Data Center edition instance

  • jira_getIssueCommentsread-only

    Get comments of a JIRA issue by its key from the JIRA Data Center edition instance

  • jira_getIssueDevelopmentInforead-only

    Get linked development information (pull requests, commits, or branches) shown in the Development panel of a JIRA issue in the JIRA Data Center edition instance. Defaults to pull requests from Bitbucket.

  • jira_getIssueLinkTypesread-only

    Get the list of available issue link types (e.g. Blocks, Relates, Duplicate) in the JIRA Data Center edition instance. Use this to discover valid link type names before calling jira_linkIssues.

  • jira_getTransitionsread-only

    Get available status transitions for a JIRA issue in the JIRA Data Center edition instance. Returns a list of transitions with their IDs, names, and target statuses.

  • jira_linkIssues

    Create a link between two JIRA issues in the JIRA Data Center edition instance. Direction is easy to invert vs the Jira UI: inwardIssueKey is the issue that DISPLAYS the outward phrase (e.g. 'blocks'); outwardIssueKey displays the inward phrase (e.g. 'is blocked by'). After create, GET the first issue — it must have outwardIssue = the second key. Use jira_getIssueLinkTypes for valid type names.

  • jira_postIssueComment

    Post a comment on a JIRA issue in the JIRA Data Center edition instance

  • jira_searchIssuesread-only

    Search for JIRA issues using JQL in the JIRA Data Center edition instance

  • jira_transitionIssue

    Transition a JIRA issue to a new status in the JIRA Data Center edition instance. Use jira_getTransitions first to get available transition IDs.

  • jira_unlinkIssues

    Delete an existing link between two JIRA issues in the JIRA Data Center edition instance. Requires the issue link id (found in the 'issuelinks' field of an issue).

  • jira_unwatchIssue

    Remove yourself (the authenticated user) as a watcher from a JIRA issue in the JIRA Data Center edition instance. Only the calling user can be removed; there is no way to unwatch on behalf of someone else.

  • jira_updateIssue

    Update an existing JIRA issue in the JIRA Data Center edition instance

  • jira_updateIssueComment

    Update the body of an existing comment on a JIRA issue in the JIRA Data Center edition instance. Use jira_getIssueComments to find the comment id.

  • jira_uploadAttachment

    Upload a local file as an attachment to a JIRA issue in the JIRA Data Center edition instance. The file must live under the server-configured upload directory; the path is given relative to that directory.

  • jira_watchIssue

    Add yourself (the authenticated user) as a watcher on a JIRA issue in the JIRA Data Center edition instance. Only the calling user can be added; there is no way to watch on behalf of someone else.

Signals

Stars
105
Forks
48
Open issues
5
Weekly downloads
2,269
Last commit
Oct 12, 2026 (16 days ago)
Last release
Oct 12, 2026 (16 days ago)
Last package publish
Oct 12, 2026 (16 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.b1ff/atlassian-dc-mcp-jira
Version
0.38.0
Auth
API key
Packages
npm @atlassian-dc-mcp/jira
License
MIT
Repository
github.com/b1ff/atlassian-dc-mcp
First seen
Oct 24, 2026
Last checked
Oct 25, 2026
Source
Official MCP Registrygithub-graphql

More from b1ff

Cite this page

Atlassian Dc MCP Jira. Agent Mart. https://agentmart.dev/connectors/b1ff-atlassian-dc-mcp-jira (last updated 2026-10-25)