# Jira Alerts (JSM Operations) [Health: Active]

**Category:** 🎧 Support & Service Management  
**Repository:** https://github.com/rrvrs/jira-alerts-mcp  
**GitHub Stars:** 4  
**npm Downloads (last month):** 574  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/jira-alerts-jsm-operations

## Description
MCP server for Jira Service Management Operations — alerts, on-call schedules and responders

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "jira-alerts-jsm-operations": {
    "command": "npx",
    "args": ["-y","jira-alerts-mcp"],
    "env": {
      "JSM_CLOUD_ID": "",
      "JSM_EMAIL": "",
      "JSM_API_TOKEN": "",
      "JSM_OAUTH_TOKEN": "",
      "JSM_TOOLSETS": "",
      "JSM_READ_ONLY": "",
      "TRANSPORT": "",
      "PORT": ""
    }
  }
}
```

**Requires environment variables:** `JSM_CLOUD_ID`, `JSM_EMAIL`, `JSM_API_TOKEN`, `JSM_OAUTH_TOKEN`, `JSM_TOOLSETS`, `JSM_READ_ONLY`, `TRANSPORT`, `PORT` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Jira Alerts (JSM Operations) MCP server does

Jira Alerts (JSM Operations) MCP server gives an MCP-compatible agent access to the alert and on-call portions of Jira Service Management Operations. It is intended for Atlassian Cloud sites with JSM Operations enabled, including environments that use JSM Operations as the alerting surface replacing Opsgenie.

The available operations cover finding alerts, reading alert notes and activity timelines, acknowledging or closing alerts, adding annotations, and assigning responders. The server also supports checking who is on call now and who is scheduled next. This makes it suitable for incident triage, status checks, and limited operational changes from an agent session.

## How it works

The published `jira-alerts-mcp` package is launched with `npx`, so a client can run it without cloning or building the repository. Node.js version 24 or newer is required. Stdio is the default transport; HTTP can be selected through configuration and listens on `127.0.0.1:3000` by default.

At startup, the server validates its credentials before completing the MCP handshake. Requests use an Atlassian Cloud site identifier and either email plus API token credentials or an OAuth 3LO bearer token. Read and write operations may require different Atlassian scopes: alert queries use the `read:ops-alert` scope, while schedule access uses `read:ops-config`.

## Setup and configuration

Jira Alerts (JSM Operations) MCP server requires `JSM_CLOUD_ID`. The cloud ID is available from the Atlassian tenant information endpoint or from the site details in the Atlassian administration console. Authentication can use `JSM_EMAIL` with `JSM_API_TOKEN`, or `JSM_OAUTH_TOKEN`; the OAuth token takes precedence when configured.

Install it in a supported MCP client with `npx -y jira-alerts-mcp`. Claude Code uses `claude mcp add` with environment variables, while Claude Desktop uses an `mcpServers` entry containing the command, arguments, and environment block. GUI-launched clients need credentials in that configuration because they may not inherit the shell environment.

`JSM_TOOLSETS` controls which tool families are registered and defaults to the responder set. `JSM_READ_ONLY=true` suppresses write tools. For HTTP mode, set `TRANSPORT=http` and optionally configure `PORT`, `HOST`, and `ALLOWED_HOSTS`. An `ALLOWED_HOSTS` value is required when binding beyond loopback.

## Tools and capabilities

The server exposes tools for:

- Listing and searching operational alerts.
- Reading alert notes and event timelines.
- Acknowledging and closing alerts.
- Adding annotations and responders.
- Listing schedules to identify current and upcoming on-call coverage.

Toolsets can be kept narrow or expanded. The documented `all` setting registers verified families for schedules, teams, maintenance windows, and routing in addition to the default responder-oriented surface. Three quarantined families are not included automatically and must be requested by name.

## Limitations and notes

Jira Alerts (JSM Operations) MCP server requires an Atlassian Cloud site with JSM Operations enabled; the material does not describe support for non-Atlassian systems or self-hosted Jira. Credentials are checked before startup, so an invalid cloud ID or token can prevent the MCP handshake entirely.

Read and schedule checks are separate: successful alert access does not guarantee that schedule access will work, because the required scopes differ. Write actions are asynchronous, so a client should verify the resulting alert state rather than assume an acknowledgement or other mutation completed. Setting read-only mode removes every write tool.

The supported installation route is the npm package via `npx`. A source checkout is described for development or unreleased revisions, but it requires installing dependencies and building the project first.

_Full upstream README: https://allmcps.com/mcp/jira-alerts-jsm-operations/readme_