Skip to main content
Glama
Jira MCP Server

Jira MCP Server

by imrnbeg

MCP Jira Server

A Model Context Protocol (MCP) server that integrates Jira with Claude Desktop, allowing you to fetch and view Jira issue details directly through Claude.

Features

  • šŸ” Get Jira Issue Details: Fetch comprehensive information about any Jira issue by its key

  • šŸ“ Browse Projects: List projects and view project details

  • 🧭 Understand Workflows: See issue types and statuses per project

  • šŸ”Ž Search Issues (JQL): Flexible search with pagination and selected fields

  • šŸ“Œ Project Issue Lists: Quickly list issues in a project

  • šŸ’¬ Issue Comments: Read comments on an issue

  • šŸ—‚ļø Agile Views: Boards, sprints, and sprint issue listings

  • šŸ” Secure Authentication: Uses Jira API tokens for secure access

  • šŸŽÆ Structured Data: Returns both human-readable and structured JSON data

  • šŸš€ Claude Desktop Integration: Seamlessly works with Claude Desktop via MCP protocol

Related MCP server: Jira MCP Server

Prerequisites

  • Node.js (v18 or higher)

  • Claude Desktop application

  • Jira instance with API access

  • Jira API token

Installation

  1. Clone the repository

    git clone https://github.com/imrnbeg/jira-mcp.git
    cd jira-mcp
  2. Install dependencies

    npm install
  3. Build the project

    npm run build

Configuration

1. Create Environment File

Create a .env file in the project root with your Jira credentials:

# .env
JIRA_URL=https://yourcompany.atlassian.net
JIRA_EMAIL=your.email@company.com
JIRA_API_TOKEN=your_api_token_here

How to get your Jira API token:

  1. Go to Atlassian Account Settings

  2. Click "Create API token"

  3. Give it a label (e.g., "MCP Server")

  4. Copy the generated token

2. Update Server Path (Important!)

āš ļø CRITICAL: You must update the .env file path in the server code to match your system.

Edit src/server.ts and update line 8:

// Change this path to match your system
loadEnvFile('/Users/imranbeg/mcp-get-server/.env');

For different systems:

  • macOS/Linux: /full/path/to/your/jira-mcp/.env

  • Windows: C:\\full\\path\\to\\your\\jira-mcp\\.env

3. Rebuild After Path Update

After updating the path, rebuild the project:

npm run build

Claude Desktop Setup

1. Locate Claude Desktop Config

macOS:

~/Library/Application Support/Claude/claude_desktop_config.json

Windows:

%APPDATA%\Claude\claude_desktop_config.json

2. Add MCP Server Configuration

Add this configuration to your Claude Desktop config file:

{
  "mcpServers": {
    "mcp-jira-server": {
      "command": "node",
      "args": ["/full/path/to/your/jira-mcp/dist/server.js"],
      "cwd": "/full/path/to/your/jira-mcp"
    }
  }
}

āš ļø Update the paths to match your system:

  • Replace /full/path/to/your/jira-mcp with your actual project path

  • Use forward slashes (/) even on Windows

3. Restart Claude Desktop

After updating the configuration, completely quit and restart Claude Desktop.

Usage

Once configured, you can use these example prompts in Claude Desktop:

Basic Issue Lookup

Get details for Jira issue PROJ-123
Show me information about ticket TASK-456
What's the status of issue BUG-789?

Detailed Issue Information

Get comprehensive details for Jira issue PROJ-123 including description, assignee, and priority
Show me the full details for ticket TASK-456 with all available information

Multiple Issues

Get details for these Jira issues: PROJ-123, TASK-456, BUG-789

Issue Status Check

What's the current status and assignee for issue PROJ-123?
Check the priority and due date for ticket TASK-456

Available Tools

get_jira_issue

Fetches detailed information about a Jira issue.

Parameters:

  • issueKey (string): The Jira issue key (e.g., PROJ-123, TASK-456)

Returns:

  • Issue summary, description, status, assignee, reporter

  • Priority, issue type, creation and update dates

  • Direct link to the issue in Jira

  • Structured JSON data for programmatic access

list_jira_projects

List accessible Jira projects with pagination and optional search query.

Parameters:

  • query (string, optional): Search by key/name

  • startAt (number, optional): Pagination start

  • maxResults (number, optional): Page size (1-100)

get_jira_project

Get full metadata for a Jira project by key or ID.

Parameters:

  • projectIdOrKey (string): Project key or ID

get_project_statuses

Get available statuses for each issue type in a project.

Parameters:

  • projectIdOrKey (string): Project key or ID

search_jira_issues

Search issues using JQL with pagination and field selection.

Parameters:

  • jql (string): JQL query

  • startAt (number, optional): Pagination start

  • maxResults (number, optional): Page size (1-100)

  • fields (string, optional): Comma-separated fields

list_project_issues

List issues in a specific project with optional extra JQL.

Parameters:

  • projectKey (string): Project key

  • jqlTail (string, optional): Extra JQL (e.g., AND status="In Progress")

  • startAt (number, optional): Pagination start

  • maxResults (number, optional): Page size (1-100)

get_jira_issue_comments

Retrieve comments for a Jira issue.

Parameters:

  • issueIdOrKey (string): Issue key or ID

  • startAt (number, optional): Pagination start

  • maxResults (number, optional): Page size (1-100)

list_boards

List Jira boards with optional filters.

Parameters:

  • type ("scrum"|"kanban", optional): Board type

  • projectKeyOrId (string, optional): Filter by project

  • startAt (number, optional): Pagination start

  • maxResults (number, optional): Page size (1-100)

list_board_sprints

List sprints on a board.

Parameters:

  • boardId (number): Board ID

  • state ("active"|"future"|"closed", optional): Sprint state

  • startAt (number, optional): Pagination start

  • maxResults (number, optional): Page size (1-100)

list_sprint_issues

List issues in a sprint with pagination.

Parameters:

  • sprintId (number): Sprint ID

  • startAt (number, optional): Pagination start

  • maxResults (number, optional): Page size (1-100)

  • jql (string, optional): Additional JQL filter

Example Prompts

Use these prompts in Claude Desktop to leverage the tools:

Project discovery

List my Jira projects.
Search Jira projects matching "platform".
Show details for project PROJ.
What issue types and statuses exist in project PROJ?

Issue search and browsing

Find issues in project PROJ assigned to me that are In Progress.
Search issues updated in the last 7 days with label "release".
List issues in project PROJ with status = "To Do".
Get comments for issue PROJ-123.

Agile views

List all Scrum boards for project PROJ.
Show active sprints on board 12.
List issues in sprint 345 ordered by priority.

Development

Running in Development Mode

npm run dev

Building for Production

npm run build

Type Checking

npm run typecheck

Troubleshooting

Server Not Loading Environment Variables

  1. Check the path in src/server.ts - Make sure it points to your actual .env file location

  2. Rebuild the project after changing the path:

    npm run build
  3. Verify .env file exists and contains valid credentials

Claude Desktop Not Connecting

  1. Check the config file paths - Ensure all paths in claude_desktop_config.json are correct

  2. Restart Claude Desktop completely

  3. Check Claude Desktop logs for connection errors

Jira API Errors

  1. Verify your API token is valid and not expired

  2. Check your Jira URL format (should include https://)

  3. Ensure your account has access to the Jira instance

Project Structure

jira-mcp/
ā”œā”€ā”€ src/
│   ā”œā”€ā”€ server.ts          # Main MCP server implementation
│   └── load-env.ts        # Custom environment loader
ā”œā”€ā”€ dist/                  # Compiled JavaScript files
ā”œā”€ā”€ .env                   # Environment variables (create this)
ā”œā”€ā”€ package.json           # Dependencies and scripts
ā”œā”€ā”€ tsconfig.json          # TypeScript configuration
└── README.md              # This file

Contributing

  1. Fork the repository

  2. Create a feature branch

  3. Make your changes

  4. Test thoroughly

  5. Submit a pull request

License

ISC License

Support

For issues and questions:

  1. Check the troubleshooting section above

  2. Review the MCP documentation

  3. Open an issue on GitHub


Happy Jira integration with Claude! šŸš€

Available Tools

10 tools
get_jira_issueGet Jira IssueC

Get detailed information about a Jira issue by its key (e.g., PROJ-123)

Inputs: issueKey (required).

get_jira_issue_commentsGet Jira Issue CommentsB

Retrieve comments for a Jira issue with pagination.

Inputs: issueIdOrKey (required), startAt, maxResults.

get_jira_projectGet Jira Project DetailsB

Get full metadata for a Jira project by key or ID.

Inputs: projectIdOrKey (required).

get_project_statusesGet Project Issue Types and StatusesC

Get available statuses for each issue type in a project.

Inputs: projectIdOrKey (required).

list_boardsList BoardsB

List Jira boards with optional type and project filter.

Inputs: type, projectKeyOrId, startAt, maxResults.

list_board_sprintsList Board SprintsB

List sprints for a given board with optional state filter.

Inputs: boardId (required), state, startAt, maxResults.

list_jira_projectsList Jira ProjectsB

List accessible Jira projects with pagination and optional query.

Inputs: query, startAt, maxResults.

list_project_issuesList Issues in ProjectB

List issues for a project with optional JQL tail filters.

Inputs: projectKey (required), jqlTail, startAt, maxResults.

list_sprint_issuesList Sprint IssuesC

List issues in a given sprint with pagination.

Inputs: sprintId (required), startAt, maxResults, jql.

search_jira_issuesSearch Jira Issues (JQL)C

Search issues using JQL with pagination and field selection.

Inputs: jql (required), startAt, maxResults, fields.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific Jira resources and actions. There is no overlap between tools like get_jira_issue (single issue details), list_project_issues (project-specific listing), and search_jira_issues (general JQL search), making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case throughout. The naming convention is predictable with verbs like 'get', 'list', and 'search' clearly indicating the action type, and nouns specifying the target resource (e.g., jira_issue, project, boards).

    Tool Count5/5

    With 10 tools, this server is well-scoped for Jira operations, covering core workflows like issue retrieval, project management, and board/sprint handling. Each tool earns its place without feeling excessive or insufficient for the domain.

    Completeness3/5

    The toolset provides strong read/search capabilities but has notable gaps in write operations. There are no tools for creating, updating, or deleting issues, comments, or other resources, which limits agents to read-only workflows and may cause failures in scenarios requiring modifications.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Jira for managing projects, issues, tasks, and workflows through the Model Context Protocol, allowing users to delegate PM tasks through Claude Desktop.
      64
      -
    • A
      license
      C
      quality
      D
      maintenance
      Connects Jira with Claude, enabling users to search issues, view issue details, update issues, add comments, and retrieve project information through natural language commands.
      1
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Jira Cloud instances for comprehensive issue management including creating, updating, searching issues, managing comments, workflow transitions, and project metadata discovery. Supports JQL queries, user search, and custom field operations with secure API token authentication.
      12
      611 npm
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude AI to interact with JIRA for project management and issue tracking, supporting JQL queries, comprehensive issue details retrieval with subtasks and linked issues, and release planning analysis.
      MIT