Log inSubmit server
Jira MCP logo

Jira MCP

by nguyenvanduocit

Connects AI clients to Jira for issue, sprint, workflow, comment, history, and development-data operations.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Jira MCP

Run the project’s own setup commands, in order.

Setup steps from the project

nguyenvanduocit/jira-mcp installs with its own commands rather than a config we can generate, so these are copied as-is. Run them in order in a terminal. Source: github.com

  1. 1. Install
    just install-cli
  2. 2. Install
    go install github.com/nguyenvanduocit/jira-mcp/cmd/jira-cli@latest
  3. 3. Start the server
    jira-mcp -env .env -http_port 3000
  4. 4. Install
    brew install nguyenvanduocit/tap/jira-mcp

Overview

The nguyenvanduocit/jira-mcp MCP server exposes Jira issue, sprint, workflow, comment, worklog, version, and development-information operations to MCP clients. It runs as a Go-based server over STDIO, with optional HTTP mode, and authenticates to Jira using an Atlassian host, email, and API token. Use it when an agent needs to search or modify Jira issues, inspect sprint state, transition workflows, or retrieve linked branches, pull requests, and commits. Tool exposure can be restricted with the ENABLED_TOOLS allowlist for narrower or read-focused deployments.

Use cases

  • Search Jira issues with JQL
  • Create and update engineering tickets
  • Inspect active and future sprints
  • Transition issues through workflows
  • Retrieve development links from Jira issues

Key features

  • JQL issue search
  • Issue creation, updates, and subtasks
  • Sprint and workflow management
  • Comments, worklogs, and history
  • Issue relationships and project versions
  • Linked branches, pull requests, and commits

Tools21

What Jira MCP lets your agent do. Expand a tool for its parameters.

Self-reported~464 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

17/17 checks healthy over the last 90d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars96Stargazers on the source repository.
Last commit6mo agoMost recent push to the default branch.
Tools exposed21Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Jira MCP works

What nguyenvanduocit/jira-mcp MCP server does

The nguyenvanduocit/jira-mcp MCP server connects an MCP-compatible AI client to Atlassian Jira. It covers common engineering and project-tracking operations rather than only issue lookup. Agents can retrieve, create, update, and search issues; create subtasks; inspect issue types and statuses; and transition issues through Jira workflows.

Sprint support includes listing active and future sprints, retrieving a sprint by ID, finding the active sprint, and searching sprint names. The server also handles comments, worklogs, issue history, linked issue relationships, project versions, and development data associated with an issue. Development information can include branches, pull requests, and commits from connected GitHub, GitLab, or Bitbucket integrations.

How it works

The server is written in Go and communicates with MCP clients through STDIO, so a local binary or Docker container does not need to expose a network port for normal use. An optional HTTP mode is available for debugging and can serve the MCP endpoint locally.

Jira access uses the Atlassian host, Atlassian email, and an API token. Each operation is exposed as a named MCP tool with typed inputs. Search uses Jira Query Language, while issue comments use Atlassian Document Format. Workflow transitions require a valid Jira transition ID.

The nguyenvanduocit/jira-mcp MCP server registers all Jira tools by default. The ENABLED_TOOLS environment variable accepts a comma-separated allowlist, allowing an administrator to expose only selected tools. Unset or empty configuration keeps the default of exposing all tools; unknown names are ignored and logged at startup.

Setup and configuration

Create an Atlassian API token through the Atlassian account security settings, then configure:

  • ATLASSIAN_HOST: the Jira instance URL
  • ATLASSIAN_EMAIL: the Atlassian account email
  • ATLASSIAN_TOKEN: the Jira API token
  • ENABLED_TOOLS: optional comma-separated tool allowlist

It also describes a local .env file for running the binary and an HTTP command using -env and -http_port flags.

Tools and capabilities

Available tool groups include:

  • Issue retrieval, creation, partial updates, subtasks, and JQL search
  • Issue types, statuses, transitions, comments, worklogs, and history
  • Related-issue lookup and issue linking
  • Sprint listing, lookup, active-sprint retrieval, and name search
  • Project-version listing and version details
  • Branch, pull-request, and commit information linked to an issue

The repository also includes a separate jira-cli binary for terminal use, but that CLI is distinct from the MCP interface.

Limitations and notes

The server requires access to a Jira instance and valid Atlassian credentials. Jira permissions and project configuration determine which issues, sprints, transitions, comments, versions, and development links are available. Mutating operations remain exposed unless the tool allowlist is configured to exclude them.

The nguyenvanduocit/jira-mcp MCP server is licensed under MIT.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Jira MCP

Docker uses the image ghcr.io/nguyenvanduocit/jira-mcp:latest, while local setup uses a built or installed jira-mcp binary.

Yes.

Set ATLASSIAN_HOST, ATLASSIAN_EMAIL, and ATLASSIAN_TOKEN. The token is an Atlassian API token.

Yes. Set ENABLED_TOOLS to a comma-separated list of the tools to register, leaving mutating tools out of the list.

Related MCP servers

All in Product Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewJira MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/nguyenvanduocit-jira-mcp?style=directory)](https://allmcps.com/mcp/nguyenvanduocit-jira-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/nguyenvanduocit-jira-mcp"><img src="https://allmcps.com/api/badge/nguyenvanduocit-jira-mcp?style=directory" alt="Jira MCP on AllMCPs" /></a>