Infrastructure Module for Linear Issue Information Retrieval

This implementation functions as a specialized MCP (Model Context Protocol) endpoint, granting controlled, non-mutating access to records within the Linear project management ecosystem. It enables sophisticated language models to query and obtain details pertaining to specific Linear tickets and their accumulated annotations by leveraging a supplied Linear authentication token.

Core Capabilities

The service exposes two distinct operational interfaces (tools):

• linear_get_issue: Designed to retrieve fundamental metadata for a Linear item, addressable either via its direct Uniform Resource Locator or its unique identifier string.
• linear_get_issue_with_comments: Offers comprehensive data acquisition for a Linear ticket, explicitly including the entire chronological sequence of user comments.

Prerequisites

To deploy and operate this component, the following environmental dependencies are mandatory:

• Node.js runtime environment
• A valid Linear API authentication credential or an OAuth scope token

Deployment Strategy

Direct software installation is obviated when employing the npx execution utility, provided Node.js and the Node Package Manager (npm) are already provisioned on the host machine.

Token Acquisition Guidance

A credential for the Linear system can be sourced through two principal avenues:

1. API Key (Most Straightforward Method): A secret key can be generated within your designated Linear API configuration panel.

2. OAuth Credential: Applicable for nuanced scenarios requiring user-specific permissions or advanced integration workflows:

3. Initiate the creation of a new OAuth 2.0 application within the Linear control center.
4. Execute the OAuth authorization flow to successfully obtain a scoped user access token.

Integration with Claude Desktop Environment

To integrate this data access mechanism with the Claude Desktop client:

1. Ensure your acquired Linear authorization key is accessible.

2. Modify the appropriate configuration file for the Claude client application:

3. MacOS Systems: ~/Library/Application Support/Claude/claude_desktop_config.json

4. Linux Systems: ~/.config/Claude/claude_desktop_config.json
5. Windows Systems: %AppData%\Claude\claude_desktop_config.json

Illustrative Configuration Snippet:

{
  "mcpServers": {
    "linear-issues": {
      "command": "npx",
      "args": ["-y", "@keegancsmith/linear-issues-mcp-server"],
      "env": {
        "LINEAR_API_TOKEN": "your_linear_api_token_here"
      }
    }
  }
}

1. The Claude application must be relaunched to recognize the new configuration settings.

Operational Demonstrations

Once the service endpoint is successfully connected, interaction within the Claude interface can proceed as follows:

Query Example 1:

Can you retrieve the specifications for issue ENG-123?

Claude is expected to invoke the linear_get_issue functionality, retrieving the necessary key from the defined environment variables.

Query Example 2:

Enumerate all textual commentary attached to the ticket located at https://linear.app/company/issue/ENG-123/issue-title?

This prompt directs Claude to employ linear_get_issue_with_comments to secure the complete manifest of the issue, inclusive of all discussion threads.

Licensing Details

This module is distributed under the terms of the MIT License.

WIKIPEDIA: XMLHttpRequest (XHR) is an API in the form of a JavaScript object whose methods transmit HTTP requests from a web browser to a web server. The methods allow a browser-based application to send requests to the server after page loading is complete, and receive information back. XMLHttpRequest is a component of Ajax programming. Prior to Ajax, hyperlinks and form submissions were the primary mechanisms for interacting with the server, often replacing the current page with another one.

== History == The concept behind XMLHttpRequest was conceived in 2000 by the developers of Microsoft Outlook. The concept was then implemented within the Internet Explorer 5 browser (1999). However, the original syntax did not use the XMLHttpRequest identifier. Instead, the developers used the identifiers ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer 7 (2006), all browsers support the XMLHttpRequest identifier. The XMLHttpRequest identifier is now the de facto standard in all the major browsers, including Mozilla's Gecko layout engine (2002), Safari 1.2 (2004) and Opera 8.0 (2005).

=== Standards === The World Wide Web Consortium (W3C) published a Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C published the Working Draft Level 2 specification. Level 2 added methods to monitor event progress, allow cross-site requests, and handle byte streams. At the end of 2011, the Level 2 specification was absorbed into the original specification. At the end of 2012, the WHATWG took over development and maintains a living document using Web IDL.

== Usage == Generally, sending a request with XMLHttpRequest has several programming steps.

Create an XMLHttpRequest object by calling a constructor: Call the "open" method to specify the request type, identify the relevant resource, and select synchronous or asynchronous operation: For an asynchronous request, set a listener that will be notified when the request's state changes: Initiate the request by calling the "send" method: Respond to state changes in the event listener. If the server sends response data, by default it is captured in the "responseText" property. When the object stops processing the response, it changes to state 4, the "done" state. Aside from these general steps, XMLHttpRequest has many options to control how the request is sent and how the response is processed. Custom header fields can be added to the request to indicate how the server should fulfill it, and data can be uploaded to the server by providing it in the "send" call. The response can be parsed from the JSON format into a readily usable JavaScript object, or processed gradually as it arrives rather than waiting for the entire text. The request can be aborted prematurely or set to fail if not completed in a specified amount of time.

== Cross-domain requests ==

In the early development of the World Wide Web, it was found possible to brea