Atlassian Jira MCP Interface Gateway

[ [

A service adhering to the Model Context Protocol specification, acting as a bridge for Jira interactions.

This gateway exposes Jira capabilities to connected Large Language Models (LLMs) using the standardized MCP framework.

Refer to the Jira REST Api Documentation for underlying API details.

Deployment Instructions

Local Setup

Prerequisite: Node.js runtime version 22.12.0 or higher is mandatory.

1. Secure your Jira Personal Access Token (PAT): Reference Guide

2. Integrate the server configuration into your Claude Desktop environment settings:

3. macOS path: ~/Library/Application Support/Claude/claude_desktop_config.json

4. Windows path: Consult this resource

Configuration Block Example (JSON):

{ "mcpServers": { "jira": { "command": "npx", "args": ["-y", "@parassolanki/jira-mcp-server@latest"], "env": { "JIRA_PERSONAL_ACCESS_TOKEN": "user_email@domain.com:your_generated_access_token", "JIRA_BASE_URL": "https://your-instance.atlassian.net" } } } }

Windows Specific Invocation:

{ "mcpServers": { "jira": { "command": "cmd /c npx", "args": ["-y", "@parassolanki/jira-mcp-server@latest"], "env": { "JIRA_PERSONAL_ACCESS_TOKEN": "user_email@domain.com:your_generated_access_token", "JIRA_BASE_URL": "https://your-instance.atlassian.net" } } } }

Available Instrumentation (Tools)

1. list_projects: Retrieves a catalog of available Jira projects.

   • Parameters:
   • query (string, optional): Filter criteria for project identification.
   • maxResults (number, optional, limit 100): Cap on the quantity of returned items.
   • expand (string, optional): Comma-delimited list for deeper data inclusion (description, lead, issueTypes, url, projectKeys, permissions, insight).

2. list_boards: Fetches agile boards associated with a specific project context.

   • Parameters:
   • projectKeyOrId (string, required): Identifier for the target project.
   • name (string, optional): Filter by board name.
   • maxResults (number, optional, limit 100): Maximum entity count.
   • startAt (number, optional): Pagination offset index.
   • type (string, optional): Board methodology filter (scrum or kanban).

3. list_sprints_from_board: Enumerates active and historical sprints tied to a board.

   • Parameters:
   • boardId (string, required): Unique identifier for the board.
   • maxResults (number, optional, limit 100): Result limit.
   • startAt (number, optional): Starting position for pagination.

4. list_issues_from_sprint: Queries the tasks contained within a specified sprint context.

   • Parameters:
   • boardId (string, required): Board identifier.
   • sprintId (string, required): Sprint identifier.
   • maxResults (number, optional, limit 100): Pagination size control.
   • startAt (number, optional): Result offset.
   • expand (string, optional): Append supplementary details (schema, names).

5. create_issue: Instantiates a new Jira ticket (currently constrained to 'Task' issue type).

   • Parameters:
   • projectKeyOrId (string, required): Target project ID or key.
   • summary (string, required): Concise title for the artifact.
   • description (string, required): Detailed content of the ticket.

Operational Flow Examples

Illustrative prompts for engaging the Jira interface:

1. "Provide a complete manifest of all Jira repositories I have access to" → Triggers list_projects.
2. "Which Kanban boards are active within the 'DEV' project structure?" → Invokes list_boards setting project to 'DEV' and type to 'kanban'.
3. "Display the chronological list of sprints linked to board ID 123" → Executes list_sprints_from_board targeting board 123.
4. "Detail the work items assigned to sprint 456 on board 123" → Utilizes list_issues_from_sprint for sprint 456/board 123 context.
5. "Retrieve the initial fifty user stories from the present active sprint on the Marketing board" → Requires sequential calls: list_boards (to find Marketing ID), list_sprints_from_board (to identify the current sprint), and finally list_issues_from_sprint with maxResults=50.

Development Lifecycle

1. Dependency acquisition:

shell pnpm install

1. Environment variable setup in .env file:

shell JIRA_PERSONAL_ACCESS_TOKEN=user_email@domain.com:your_generated_access_token JIRA_BASE_URL=https://your-instance.atlassian.net

1. Launch in development mode with hot-reloading:

shell pnpm dev

1. Production build compilation:

shell pnpm build

1. Debugging invocation via inspector:

shell pnpm inspector

Future Enhancements (TODO List)

• [x] Project listing functionality (list_projects)
• [x] Board enumeration (list_boards)
• [x] Sprint retrieval by board (list_sprints_from_board)
• [x] Issue fetching from sprint context (list_issues_from_sprint)
• [ ] Specific artifact lookup by identifier (get_issue_by_id_or_key)
• [x] Issue artifact creation (limited to Task type) (create_issue)
• [ ] Expanded artifact creation support (Story, Epic, Sub-task)
• [ ] Artifact modification procedures (update_issue)
• [ ] Artifact removal capability (delete_an_issue)
• [ ] Issue archival mechanism (archieve_an_issue)
• [ ] Comment listing for an issue (list_comments_from_issue)
• [ ] Fetching a singular comment by ID (get_comment_from_issue_by_id)
• [ ] Comment submission to an issue (create_comment_in_issue)
• [ ] Comment revision (update_comment_of_issue)
• [ ] Comment deletion (delete_comment_of_issue)
• [ ] Sub-task enumeration for a parent issue (list_subtasks_from_issue)
• [ ] User lookup based on identifier (get_user_by_username_or_key)

WIKIPEDIA CONTEXT: Business management tools encompass the systems, applications, controls, computational frameworks, and organizational methodologies deployed by enterprises to navigate market volatility, maintain competitive positioning, and optimize overall operational performance. These tools span departmental functions—including strategic planning, workflow control, data record-keeping, personnel management, complex decision support, and performance monitoring. Modern business software has rapidly evolved from early Management Information Systems (MIS) through Enterprise Resource Planning (ERP) and Customer Relationship Management (CRM) platforms into today's cloud-based management suites. Value addition hinges not just on IT investment, but crucially on effective implementation strategies and the judicious selection and customization of the tools to fit the organization's unique requirements, rather than forcing organizational structure around off-the-shelf software.

== Frequently Leveraged Business Instruments (Survey Data) == Based on a 2013 Bain & Company global survey, the most prevalent instruments selected by organizations include:

• Strategic Planning Frameworks
• Customer Relationship Management (CRM) Systems
• Employee Feedback Mechanisms (Surveys)
• Competitive Benchmarking
• Balanced Scorecard Implementation
• Core Competency Analysis
• Outsourcing Strategy Definition
• Change Management Programs
• Supply Chain Optimization
• Mission and Vision Articulation
• Market Segmentation Analysis
• Total Quality Management (TQM)

== Software Applications in Enterprise Operations == Business software refers to computational packages utilized by personnel to execute diverse corporate functions, aiming to enhance throughput, quantify results, and ensure operational precision. The progression moved from initial MIS toward integrated ERP, followed by the integration of CRM functionalities, culminating in contemporary cloud-native business management platforms. Achieving measurable performance gains requires aligning IT strategy with the organization's core objectives, emphasizing both the method of deployment and the careful selection process for the utilized applications.