Jira Alerts (JSM Operations) MCP Server

An MCP server for Jira Service Management Operations — the alert surface that replaced Opsgenie, which no other Jira MCP server covers.

Local serverstdioApache-2.0

What is the Jira Alerts (JSM Operations) MCP Server?

jira-alerts-mcp is an MCP project maintained in the rrvrs/jira-alerts-mcp repository. The maintainer describes its purpose as “An MCP server for Jira Service Management Operations — the alert surface that replaced Opsgenie, which no other Jira MCP server covers”. Read the project documentation for the complete scope.

Installation

The documented npm package is jira-alerts-mcp. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.

Configuration values

The example declares JSM_CLOUD_ID, JSM_EMAIL, JSM_API_TOKEN, JSM_TOOLSETS. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.

Source

Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.

How to install the Jira Alerts (JSM Operations) MCP Server

{
  "mcpServers": {
    "jira-alerts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "jira-alerts-mcp"
      ],
      "env": {
        "JSM_CLOUD_ID": "your-cloud-id",
        "JSM_EMAIL": "you@example.com",
        "JSM_API_TOKEN": "YOUR_JSM_API_TOKEN",
        "JSM_TOOLSETS": "all"
      }
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Configuration

VariableDescriptionRequired
JSM_CLOUD_IDDeclared in the maintainer’s client configuration.Check documentation
JSM_EMAILDeclared in the maintainer’s client configuration.Check documentation
JSM_API_TOKENDeclared in the maintainer’s client configuration.Check documentation
JSM_TOOLSETSDeclared in the maintainer’s client configuration.Check documentation