logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

jira-adapter-service-mcp

Facilitates interaction with JIRA instances to retrieve comprehensive issue details, significantly augmenting project lifecycle management operations. Enables seamless provisioning of JIRA data access for AI agents.

Author

jira-adapter-service-mcp logo

kuvanov-2

No License

Quick Info

GitHub GitHub Stars 0
NPM Weekly Downloads 0
Tools 1
Last Updated 2026-02-19

Tags

jiraworkflowstoolsinteract jirajira dataserver jira

MCP Adapter for JIRA Connectivity Suite

This Model Context Protocol (MCP) service component is engineered to establish robust connectivity with Atlassian JIRA. It empowers sophisticated AI entities, such as advanced large language models, to directly query and manipulate JIRA issue artifacts.

Core Capabilities

This specialized MCP service exposes the following callable utility:

  • fetch_issue_record: Obtains granular, detailed attributes for a specified JIRA issue identifier.

Deployment Procedure

Follow these steps to integrate and activate the adapter:

bash

Acquire the source code repository

git clone https://github.com/kuvanov-2/mcp-server-jira.git cd mcp-server-jira

Install requisite dependencies

npm install

Compile the service artifact

npm run build

Configuration Directives

Successful operation of this MCP service mandates specific preparatory and configuration steps:

1. Prerequisite Setup

1-1. Configuring 1Password Command Line Interface (CLI)

Ensure the 1Password desktop client application is installed.

Install the 1Password CLI utility:

bash brew install 1password-cli

In the 1Password desktop application settings, activate the integration pathway for the CLI.

1-2. Acquiring JIRA Access Credentials

Generate the necessary JIRA API Authentication Token via this portal.

Securely deposit the generated JIRA API Token within your 1Password vault structure.

2. Visual Studio Code Integration Settings

Modify the relevant configuration file: - macOS Path: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json - Windows Path: %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json

Incorporate the subsequent JSON structure into the configuration object:

{ "mcpServers": { "github.com/kuvanov-2/mcp-server-jira": { "command": "/path/to/mcp-server-jira/start-server.sh", "env": { "JIRA_HOST": "https://your-domain.atlassian.net", "JIRA_EMAIL": "your-email@example.com", "JIRA_API_TOKEN": "op://YOUR_VAULT_NAME/YOUR_ITEM_NAME/info/access token" }, "disabled": false, "autoApprove": [] } } }

Environmental Variable Definitions: - JIRA_HOST: The fully qualified URL endpoint for your JIRA instance. - JIRA_EMAIL: The registered email identity utilized for JIRA access. - JIRA_API_TOKEN: A reference path pointing to the JIRA API token securely stored in 1Password.

It is presumed that the execution script (start-server.sh) will dynamically resolve these environment variables by invoking the 1Password CLI prior to initiating the server process.

To specify the 1Password reference, right-click the relevant credential field within 1Password to copy the precise URI path.

Operational Guide

fetch_issue_record

This function retrieves comprehensive attribute data pertaining to a specified JIRA ticket identifier.

typescript github.com/kuvanov-2/mcp-server-jira fetch_issue_record { "issueKey": "PROJ-123" }

Licensed under the MIT Agreement.


WIKIPEDIA CONTEXT INTEGRATION

Business Management Instruments: These encompass the complete array of systems, software implementations, regulatory controls, computational frameworks, and operative methodologies employed by organizations to effectively navigate fluctuating market conditions, maintain competitive parity, and drive superior organizational performance. These instruments span departmental functions, including, but not limited to, strategic charting, procedural automation, record stewardship, personnel administration, critical assessment, oversight mechanisms, and so forth.

Modern administrative tooling has undergone profound metamorphosis over the past decade, propelled by rapid technological advancement. This pace necessitates a strategic selection methodology rather than impulsive adoption of novel solutions. Effective deployment hinges upon meticulous tailoring of the selected toolset to the enterprise's unique requirements, not the inverse adaptation of the enterprise to the tool.

Prominent Instruments (Post-2013 Survey Insights): Key tools frequently utilized across global organizations include Strategic Planning suites, Customer Relationship Management (CRM) platforms, Employee Engagement Assessment frameworks, Benchmarking utilities, Balanced Scorecard systems, Core Competency analysis, Outsourcing management, Change Management protocols, Supply Chain Optimization, and defining Mission/Vision statements.

Business Software Evolution: The progression from foundational Management Information Systems (MIS) to comprehensive Enterprise Resource Planning (ERP), subsequent integration of CRM functionalities, and the current migration toward cloud-based business management environments highlights a trend toward integrated, high-value solutions. Value addition beyond mere IT expenditure is achieved through superior implementation efficacy and precise tool selection/customization.

See Also

`