Does nguyenvanduocit/jira-mcp work with Claude Desktop?

Yes. Claude Desktop is named as a supported installation target, although the provided material does not include a dedicated configuration example.

What credentials does the nguyenvanduocit/jira-mcp MCP server need?

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

Can I expose only read-only Jira tools with nguyenvanduocit/jira-mcp?

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

Jira MCP

jiraissue-trackingsprintsdeveloper-tools

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

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "nguyenvanduocit-jira-mcp": {
      "command": "docker",
      "args": [
        "run",
        "ghcr.io/nguyenvanduocit/jira-mcp:latest"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

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

Capabilities & Tool Schemas (21)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by Jira MCP.

jira_get_issue

Retrieve detailed information about a specific issue including status, assignee, description, subtasks, and available transitions

jira_create_issue

Create a new issue with specified details (returns key, ID, and URL)

jira_create_child_issue

Create a child issue (sub-task) linked to a parent issue

jira_update_issue

Modify an existing issue's details (supports partial updates)

jira_list_issue_types

List all available issue types in a project with their IDs, names, and descriptions

jira_search_issue

Search for issues using JQL (Jira Query Language) with customizable fields and expand options

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

The README documents Docker and local-binary configurations for Cursor, with the credentials passed as environment variables. It also describes a local .env file for running the binary and an HTTP command using -env and -http_port flags. Claude Desktop is named as an installation target, but the supplied material does not provide a dedicated Claude configuration example.

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 provided material does not specify support for OAuth, Jira Server/Data Center compatibility, or the exact permission requirements for each operation.

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

Read the full README →View source on GitHub →

Related MCP Servers

View all in Support & Service Management View all alternatives

Adoption & maintenance

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

GitHub stars

Stargazers on the source repository.

Last commit

4mo ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

3 views

Config copies, upvotes, and views on AllMCPs.

Reviews

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

Frequently Asked Questions about Jira MCP

The README documents Docker and local-binary setup for MCP clients. Docker uses the image ghcr.io/nguyenvanduocit/jira-mcp:latest, while local setup uses a built or installed jira-mcp binary.

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 Preview

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>

Technical Specs & Signals

CategorySupport & Service Management

PricingFree

59Quality signal: Good · 59/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools29/30

Adoption & activity5/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🎧 Support & Service Management →Alternatives to Jira MCP →Install in Claude Desktop Install in Cursor Install in VS Code