Jira MCP Server

Community

Interact with Jira using natural language to manage projects efficiently.

How to install ↓ Compare GitHub source repository ↗

Category: Collaboration #44 of 55
Stars: ★ 64 Popular
Transport: stdio (local process)
Runtime: Node.js
Credentials: API key / credential required
Last commit: 13 months ago ⚠
Tools: 11

42FMRS · D

This MCP server simplifies Jira operations through natural language, suitable for teams using Jira. It provides comprehensive issue management features, but requires valid credentials and attention to delete operation risks.

Strongest · Documentation 12/20 Weakest · Reliability 6/20

Reliability

6/20

Security and permissions

8/20

Maintenance

6/20

Documentation

12/20

Setup experience

10/20

Why each score

Reliability 6/20: Source shows MCP server initialization and tool definitions, but not executed or verified. Error handling and test coverage appear thin; no tests or CI workflows present. Thus below 12.
Security and permissions 8/20: Auth methods documented (basic/bearer) but least-privilege guidance and explicit confirmation for delete operations are lacking. No red flags for malware or credential exposure.
Maintenance 6/20: Project shows some activity but license unknown and no evidence of regular releases or dependency updates. Maintenance score reflects gaps.
Documentation 12/20: README provides detailed install, auth, and tool parameter guidance with client config examples, but lacks troubleshooting and limitation sections.
Setup experience 10/20: Setup instructions are clear with examples for multiple clients, but lacking CI or test verification keeps score below 15.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

Teams using Jira for project management
Users who want to manage tasks via natural language with AI assistants
Developers needing to automate common PM operations like assignment and status updates

Not for

Users who do not use Jira
Scenarios requiring complex permission management
Developers who need direct API access without natural language interaction

Required permissions

Read access to Jira projects, issues, and user information
Create, update, and delete issues and subtasks
Create issue links (dependencies)
Requires JIRA_HOST, JIRA_API_TOKEN or PAT, and JIRA_EMAIL for basic auth

Risks and side effects

If API tokens are leaked, attackers can access and modify Jira data
Delete operations are irreversible and may cause data loss, especially when deleting subtasks
Misconfiguration may lead to permission issues or API rate limits
Dependent on Jira API version, subject to instance limitations

Setup

Before you start

Runtime：Node.js

JIRA_HOST required Your Jira instance hostname, e.g. your-jira-instance.atlassian.net

JIRA_EMAIL required Your Jira account email; required when using basic auth

JIRA_API_TOKEN requiredsecret API token (from https://id.atlassian.com/manage-profile/security/api-tokens) or a Personal Access Token; secret

Other optional settings (2)

JIRA_AUTH_TYPE optional Auth type, basic (default) or bearer (when using a PAT); optional

JIRA_API_VERSION optional Jira API version, defaults to 3; optional

Clone the repository: git clone https://github.com/George5562/Jira-MCP-Server.git
Install dependencies: npm install
Configure environment variables: Create a .env file with JIRA_HOST, JIRA_API_TOKEN, and JIRA_AUTH_TYPE (optional JIRA_EMAIL for basic auth)
Build the project: npm run build
Start the server: npm start

For Claude Desktop, add the mcpServers entry to the configuration file (claude_desktop_config.json).

claude_desktop_config.json

{
  "mcpServers": {
    "jira-server": {
      "command": "node",
      "args": [
        "/path/to/jira-server/build/index.js"
      ],
      "cwd": "/path/to/jira-server",
      "env": {
        "JIRA_HOST": "your-jira-instance.atlassian.net",
        "JIRA_EMAIL": "[email protected]",
        "JIRA_API_TOKEN": "your-api-token",
        "JIRA_AUTH_TYPE": "basic"
      }
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

{
  "servers": {
    "jira-server": {
      "command": "node",
      "args": [
        "/path/to/jira-server/build/index.js"
      ],
      "cwd": "/path/to/jira-server",
      "env": {
        "JIRA_HOST": "your-jira-instance.atlassian.net",
        "JIRA_EMAIL": "[email protected]",
        "JIRA_API_TOKEN": "your-api-token",
        "JIRA_AUTH_TYPE": "basic"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add jira-server -e JIRA_HOST=your-jira-instance.atlassian.net -e [email protected] -e JIRA_API_TOKEN=your-api-token -e JIRA_AUTH_TYPE=basic -- node /path/to/jira-server/build/index.js

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After restarting the client, tools such as CreateIssue and GetIssuesFromProject should appear in the tool list; alternatively ask 'list issues in the PROJECT project' — a returned issue list proves the connection works.

Troubleshooting

If connection fails, check that JIRA_HOST is correct (e.g., your-instance.atlassian.net), JIRA_API_TOKEN is valid, JIRA_AUTH_TYPE is set correctly (basic or bearer), and network connectivity to the Jira instance is available. For PAT, ensure PAT support is enabled.

Things to try

Once connected, you can ask your AI assistant things like:

Using Jira MCP, list all issues in the PROJECT project that are In Progress
Look up the Jira account ID for [email protected] and assign PROJECT-123 to them
Create a new Task in PROJECT titled 'Fix login page bug' with High priority and add two subtasks to it
Delete PROJECT-123 along with all of its subtasks

Tools 11

GetUserByEmail read-only

Get a user's account ID by email.

GetAllIssueTypes read-only

List all available issue types.

GetAllIssueLinkTypes read-only

List all available issue link types.

GetIssuesFromProject read-only

Get issues from a project with optional JQL filtering.

CreateIssue writes

Create a standard issue.

CreateSubtask writes

Create a subtask.

UpdateIssue writes

Update issue fields.

CreateIssueLink writes

Create a link between issues.

Show 3 more tools

DeleteIssue destructive

Delete a single issue.

DeleteIssueWithSubtasks destructive

Delete an issue along with its subtasks.

DeleteMultipleIssues destructive

Delete multiple issues at once.

Use cases

List all issues in a project

Create new issues or subtasks and assign them to team members

Query issues with JQL, such as tasks assigned to me

Update issue status, priority, description, etc.

Establish dependencies between issues (e.g., blocks/is blocked by)

Supported clients

Claude Desktop

Cursor

Listed from the project's documentation, not tested by this site.

Overview

This is an MCP server that enables interaction with Jira using natural language, allowing users to retrieve information and modify projects. It supports project creation and configuration, issue and subtask management, issue linking and dependencies, and automated issue workflows.

Similar servers

Atlassian Rovo MCP Server 66 · C

Securely connect Atlassian Cloud to AI tools.

★ 1.1k Compare with this →

Notion MCP Server 64 · C

Official Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.

★ 4.7k · Tools 9 Compare with this →

WhatsApp Channel for Claude Code 64 · C

Drive your Claude Code session straight from WhatsApp

★ 104 · Tools 10 Compare with this →

Anytype MCP Server 64 · C

Official MCP server that lets AI assistants manage your encrypted Anytype wiki in natural language.

★ 532 Compare with this →

Compare with other MCP servers

Source revision 009afb88f276 Data synced 2026-10-13 Read the FMRS scoring method