Jira Data Center

A Model Context Protocol (MCP) server that connects AI assistants to Jira Server/Data Center. Create and manage issues, search with JQL, track sprints, and interact with your Jira instance through natural language in Claude and other AI assistants.

[!IMPORTANT] This is an archival recovery of the original [email protected] npm distribution by Evrim Alacan. It is not the original source repository and is not affiliated with the original author. The published JavaScript, type declarations, and source maps are preserved; the unpublished TypeScript source, tests, and Git history are not available. See PROVENANCE.md.

Quick Start

Run Directly from GitHub

npx --yes \
  --package='github:Yiivgeny/mcp-jira-data-center#v1.0.6' \
  mcp-jira-data-center

Install it as a dependency:

npm install 'github:Yiivgeny/mcp-jira-data-center#v1.0.6'

For the exact original npm tarball, use the asset attached to the v1.0.6 GitHub Release.

Get Your Jira Server Credentials

1. Log into your Jira Server instance
2. Go to Profile > Personal Access Tokens
3. Click Create token
4. Give it a name and copy the generated token
5. Note your Jira Server URL (e.g., https://jira.yourcompany.com)

Configuration

Claude Code

Add the server using the Claude Code CLI:

claude mcp add -s user \
    jira-server \
    npx --yes --package='github:Yiivgeny/mcp-jira-data-center#v1.0.6' mcp-jira-data-center \
    -e "JIRA_URL=https://jira.yourcompany.com" \
    -e "JIRA_TOKEN=your_personal_access_token"

Manual Configuration (Any MCP Client)

Add this configuration to your MCP client's configuration file:

{
  "mcpServers": {
    "jira-server": {
      "command": "npx",
      "args": [
        "--yes",
        "--package=github:Yiivgeny/mcp-jira-data-center#v1.0.6",
        "mcp-jira-data-center"
      ],
      "type": "stdio",
      "env": {
        "JIRA_URL": "https://jira.yourcompany.com",
        "JIRA_TOKEN": "your_personal_access_token"
      }
    }
  }
}

Available Tools

The server provides 29 MCP tools for Jira Server operations:

Issues (15 tools)

• get_issue - Get issue details by key or ID
• search_issues - Search issues with JQL
• create_issue - Create a new issue
• update_issue - Update issue fields (single JSON fields param)
• delete_issue - Delete an issue
• add_comment - Add a comment to an issue
• edit_comment - Edit an existing comment
• transition_issue - Transition an issue to a new status
• get_transitions - Get available transitions for an issue
• link_to_epic - Link an issue to an epic
• get_worklog - Get worklogs for an issue
• add_worklog - Add a worklog entry
• download_attachments - Download all attachments from an issue
• batch_get_changelogs - Get changelogs for multiple issues
• batch_create_issues - Create multiple issues at once

Projects (2 tools)

• get_all_projects - List all accessible projects
• get_project_versions - Get versions for a project

Agile (6 tools)

• get_agile_boards - List agile boards
• get_board_issues - Get issues on a board
• get_sprints_from_board - List sprints for a board
• get_sprint_issues - Get issues in a sprint
• create_sprint - Create a new sprint
• update_sprint - Update sprint details

Fields (2 tools)

• search_fields - Search for field definitions
• get_field_options - Get allowed values for a field

Links (3 tools)

• get_link_types - List available issue link types
• create_issue_link - Link two issues together
• remove_issue_link - Remove a link between issues

Users (1 tool)

• get_user_profile - Get user profile by username

Example Queries

• "Show me all open bugs in the PROJ project"
• "Create a bug report for the login page issue"
• "What are the active sprints on the main board?"
• "Transition PROJ-123 to In Progress"
• "Add a comment to PROJ-456 with the investigation results"
• "Download all attachments from PROJ-789"
• "Link PROJ-100 to epic PROJ-50"

Archive Contents

This repository contains the installable compiled distribution: readable ESM JavaScript, TypeScript declarations, and source maps under dist/. It can be installed and run as a package without rebuilding. It does not contain the original TypeScript source tree or development configuration.

Troubleshooting

Common Issues

"Authentication failed"

• Verify your Personal Access Token is correct
• Ensure the token has not expired

"Access forbidden"

• Check your Jira user has permission for the resource
• Verify project-level permissions

"Resource not found"

• Confirm the issue key, project key, or ID is correct
• Check you have access to the specified resource

Documentation

• Archive provenance - Recovery details and verified checksums
• Jira Server REST API - Official API reference
• Model Context Protocol - MCP specification

License

MIT License - see LICENSE. Original package author: Evrim Alacan.