home / mcp / jira insights mcp server

Jira Insights MCP Server

A Model Context Protocol (MCP) server for managing Jira Insights (JSM) asset schemas, object types, and objects with AQL query support.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "aaronsb-jira-insights-mcp": {
      "command": "node",
      "args": [
        "/path/to/jira-insights-mcp/build/index.js"
      ],
      "env": {
        "LOG_MODE": "strict",
        "JIRA_HOST": "https://your-domain.atlassian.net",
        "JIRA_EMAIL": "[email protected]",
        "JIRA_API_TOKEN": "your-api-token"
      }
    }
  }
}

You use this MCP server to manage Jira Insights (JSM) asset schemas through the Model Context Protocol. It lets you create, read, update, and delete object schemas, object types, and objects, and to query data with AQL in a Jira Insights environment.

How to use

You can run this MCP server locally for development or deploy it via Docker. Your MCP client will interact with the Jira Insights MCP to perform schema, object type, and object operations, as well as run AQL queries against Jira Insights assets.

Two deployment methods are provided to start the MCP server. Choose the local build configuration if you want to run the server directly from your machine, or use the Docker configuration for a containerized setup. Both configurations require you to supply Jira Insights credentials and host details so the MCP can access your Jira data.

How to install

Prerequisites you need before installing the MCP server are:

Node.js 20 or later
Docker (for containerized deployment)
Jira Insights instance with API access
Jira API token with appropriate permissions

Step-by-step local development setup (clone, install, build):

# 1) Clone the repository
git clone https://github.com/aaronsb/jira-insights-mcp.git
cd jira-insights-mcp

# 2) Install dependencies
npm install

# 3) Build the project
npm run build

Docker-based deployment uses the provided image. Build is available via the local build script, and you can run the container with the required Jira credentials and host information.

# Build the Docker image for local development
./scripts/build-local.sh

# Run the container locally (example)
JIRA_API_TOKEN=your_token JIRA_EMAIL=your_email JIRA_HOST=your_host ./scripts/run-local.sh

Configuration and usage notes

You configure how the MCP server starts and what environment it uses. Below are explicit configuration examples for both a local build start and a Docker-based start. Each configuration includes the necessary environment variables.

{
  "mcpServers": {
    "jira-insights": {
      "command": "node",
      "args": ["/path/to/jira-insights-mcp/build/index.js"],
      "env": {
        "JIRA_API_TOKEN": "your-api-token",
        "JIRA_EMAIL": "[email protected]",
        "JIRA_HOST": "https://your-domain.atlassian.net",
        "LOG_MODE": "strict"
      }
    }
  }
}

{
  "mcpServers": {
    "jira-insights": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e", "JIRA_API_TOKEN",
        "-e", "JIRA_EMAIL",
        "-e", "JIRA_HOST",
        "ghcr.io/aaronsb/jira-insights-mcp:latest"
      ],
      "env": {
        "JIRA_API_TOKEN": "your-api-token",
        "JIRA_EMAIL": "[email protected]",
        "JIRA_HOST": "https://your-domain.atlassian.net"
      }
    }
  }
}

Running locally for development

For local development and testing, build the Docker image and run the container with your Jira credentials and host information.

# Build the Docker image
./scripts/build-local.sh

# Run the Docker container with credentials
JIRA_API_TOKEN=your_token JIRA_EMAIL=your_email JIRA_HOST=your_host ./scripts/run-local.sh

Available tools

manage_jira_insight_schema

Manage Jira Insights object schemas with CRUD operations.

manage_jira_insight_object_type

Manage Jira Insights object types with CRUD operations.

manage_jira_insight_object

Manage Jira Insights objects with CRUD operations and AQL queries.