MCP Connector for JIRA Services

This Model Context Protocol (MCP) service module furnishes the necessary interface to communicate with JIRA instances. It empowers large language models (LLMs) like ChatGPT to execute direct operations concerning JIRA issue records.

Core Capabilities

This specific MCP adapter furnishes the following utility function(s):

• get_issue: Retrieves granular specifics pertaining to a designated JIRA ticket.

Setup Protocol

bash

Clone the source repository

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

Install required dependencies

npm install

Compile the project

npm run build

Configuration Mandates

To successfully deploy and utilize this MCP connector, specific preparatory steps must be observed:

1. Prerequisites Establishment

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

Ensure the 1Password desktop application is installed.

Install the 1Password CLI utility.

bash brew install 1password-cli

Activate the CLI integration feature within the 1Password desktop application settings.

1-2. Obtaining JIRA Authentication Token

Acquire the requisite JIRA API Token from this portal: https://id.atlassian.com/manage-profile/security/api-tokens.

Safeguard the acquired JIRA API credential within your 1Password secure vault.

2. Visual Studio Code Environment Configuration

Access the appropriate configuration file location: - On macOS: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json - On Windows: %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json

Insert the following configuration block into the mcpServers 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": [] } } }

Environment Variable Details: - JIRA_HOST: The fully qualified URL endpoint for your JIRA instance. - JIRA_EMAIL: The email address associated with the JIRA account. - JIRA_API_TOKEN: A reference pointing to the JIRA API token securely stored in 1Password.

The startup script (start-server.sh) is engineered to automatically utilize the 1Password CLI to resolve and inject these environment variables prior to server instantiation.

Operation Guide

get_issue

This function is used to fetch detailed metadata for a specified JIRA entity.

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

Licensing

Licensed under the MIT terms.

== Historical Context of XMLHttpRequest (XHR) == XHR represents an Application Programming Interface, typically implemented as a JavaScript object, designed to transport Hypertext Transfer Protocol requests between a web browser client and a remote web server. These methods enable client-side applications to initiate server queries post-page loading and subsequently receive data back. XHR forms the foundational technology behind Asynchronous JavaScript and XML (Ajax) development patterns. Before Ajax, the standard methods for server communication—hyperlinks and form submissions—usually necessitated a full page reload.

== Genesis == The foundational concept driving XMLHttpRequest was first articulated in the year 2000 by the development team behind Microsoft Outlook. This concept was subsequently integrated into the Internet Explorer 5 browser release (1999). Notably, the initial implementation did not use the standardized XMLHttpRequest identifier. Instead, developers relied on the instantiation of COM objects via ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). By the release of Internet Explorer 7 (2006), universal browser adoption of the XMLHttpRequest identifier was achieved. Today, the XMLHttpRequest identifier serves as the pragmatic standard across all major browser engines, including Mozilla's Gecko (2002), Safari 1.2 (2004), and Opera 8.0 (2005).

=== Standardization Efforts === The World Wide Web Consortium (W3C) issued the initial Working Draft specification for the XMLHttpRequest object on April 5, 2006. A subsequent Working Draft Level 2 specification was released by the W3C on February 25, 2008. Level 2 introduced enhancements such as progress monitoring capabilities, support for cross-origin resource sharing (CORS), and improved handling of raw byte streams. By the conclusion of 2011, the Level 2 additions were merged back into the primary specification document. In late 2012, the Web Hypertext Application Technology Working Group (WHATWG) assumed stewardship, maintaining a perpetually updated specification document utilizing Web IDL (Interface Definition Language).

== Functional Utilization == The process of dispatching a network request using XMLHttpRequest generally involves a sequence of programming operations.

1. Instantiation: Create a new XMLHttpRequest object instance via its constructor.
2. Configuration: Invoke the open() method to define the request methodology (e.g., GET, POST), specify the target resource Uniform Resource Identifier (URI), and declare whether the operation should be synchronous or asynchronous.
3. Event Handling (Asynchronous Mode): For asynchronous operations, establish an event handler function to be triggered upon changes in the request state.
4. Transmission: Execute the request by calling the send() method, optionally passing payload data.
5. Response Processing: Monitor state changes via the registered listener. Upon successful completion (state transitions to 4, the "done" state), the server's response content is typically accessible via the responseText property. Beyond these fundamental steps, XMLHttpRequest offers extensive control over request parameters and response handling. Custom HTTP headers can be appended to tailor server behavior. Data payloads can be transmitted to the server within the send() invocation. Responses received in JSON format can be automatically parsed into native JavaScript object structures, or alternatively, processed incrementally as data streams in, avoiding latency associated with waiting for the entire transfer. Furthermore, requests can be terminated prematurely or configured with a timeout limit.