Jira Aio MCP Server

🚀 AIO MCP Server

An MCP (Model Context Protocol) server for interacting with the Jira AIO (All-in-One) test case management system.

🚀 Quick Start

This is an MCP server designed to interact with the Jira AIO test case management system, enabling users to access detailed test case information, search for test cases, and obtain project folder structures.

✨ Features

• Retrieve detailed information about AIO test cases.
• Search for test cases by project and/or folder.
• Obtain the folder structure of a project.
• Get a list of all projects in AIO.

📦 Installation

Prerequisites

• Node.js
• Access to a Jira instance with the AIO test case management system installed.
• A Jira API token.

Steps

1. Clone the repository.
2. Install the dependencies:

npm install

3. Build the project:

npm run build

📚 Documentation

Configuration

The server needs to be configured via mcp.json. You can place this file in one of the following locations:

• User's home directory: ~/.cursor/mcp.json
• Project root directory

Example mcp.json configuration:

{
  "jira-aio": {
    "command": "node",
    "args": ["/path/to/aio-server-mcp/build/index.js"],
    "env": {
      "JIRA_URL": "https://your-jira-instance:port",
      "JIRA_TOKEN": "your-base64-encoded-token"
    }
  }
}

Configuration Parameters

Available Tools

1. get_aio_testcase

Retrieve detailed information about a specific test case.

• Parameters:
  • projectKey: The project key in AIO (e.g., "AT").
  • testCaseKey: The test case key (e.g., "AT-TC-9").

2. search_aio_testcase

Search for test cases in a project and specific folders.

• Parameters:
  • projectId: The project ID in AIO (e.g., 11502).
  • folderIds: (Optional) An array of folder IDs to search within.

3. get_aio_folders

Obtain the folder structure of a project.

• Parameters:
  • projectId: The project ID in AIO (e.g., 11502).

4. get_aio_projects

Get a list of all available projects in AIO.

• No parameters required.

🔧 Technical Details

Error Handling

The server includes comprehensive error handling capabilities, including:

• API request failures
• Authentication issues
• Invalid configurations
• Missing required parameters

Security

• The server uses authentication with a bearer token.
• It supports HTTPS connections.
• Sensitive configurations can be provided via environment variables.

Development

The server is built using the following technologies:

• TypeScript
• Model Context Protocol SDK
• Axios for HTTP requests