Log inSubmit server
Jira Alerts (JSM Operations) logo

Jira Alerts (JSM Operations)

Connects an agent to Jira Service Management Operations for alert handling, responder management, and on-call lookups.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Jira Alerts (JSM Operations)

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "jira-alerts-jsm-operations": {
      "command": "npx",
      "args": [
        "-y",
        "jira-alerts-mcp"
      ],
      "env": {
        "JSM_CLOUD_ID": "YOUR_VALUE_HERE",
        "JSM_EMAIL": "YOUR_VALUE_HERE",
        "JSM_API_TOKEN": "YOUR_VALUE_HERE",
        "JSM_OAUTH_TOKEN": "YOUR_VALUE_HERE",
        "JSM_TOOLSETS": "YOUR_VALUE_HERE",
        "JSM_READ_ONLY": "YOUR_VALUE_HERE",
        "TRANSPORT": "YOUR_VALUE_HERE",
        "PORT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y jira-alerts-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 17d ago.

Overview

Jira Alerts (JSM Operations) MCP server connects agents to Jira Service Management Operations on Atlassian Cloud. It supports alert search, notes and activity timelines, acknowledgements, closures, annotations, responder additions, and on-call schedule lookups. The server runs through the published npm package over MCP, with stdio as the default transport and optional HTTP transport. Reach for it when an agent needs to inspect or update operational alerts and identify current or upcoming on-call coverage.

Use cases

  • List open operational alerts
  • Read an alert’s notes and activity timeline
  • Acknowledge or close an alert
  • Add responders to an alert
  • Check current and upcoming on-call coverage

Key features

  • Search and list JSM Operations alerts
  • Read alert notes and activity timelines
  • Acknowledge, close, and annotate alerts
  • Add alert responders
  • Look up current and next on-call schedules
  • Support stdio and optional HTTP transport

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

10/10 checks healthy over the last 55d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · jira-alerts-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads574Package downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Jira Alerts (JSM Operations) works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Jira Alerts (JSM Operations)

Jira Alerts (JSM Operations) is an MCP server that connects an agent to Jira Service Management Operations on Atlassian Cloud. Its main tools list and search alerts, read notes and activity timelines, acknowledge or close alerts, add responders, and check who is on call now or next. It runs from the published npm package.

Install it with `npx -y jira-alerts-mcp` through your MCP client. Configure the client with `JSM_CLOUD_ID` and either email plus API token or an OAuth token. Node.js 24 or newer and a Jira Service Management site with Operations enabled are required.

Yes, it works with Claude Desktop through an `mcpServers` configuration entry. Add the `npx` command, package argument, and required environment variables, then fully quit and reopen Claude Desktop so it reads the configuration.

Schedule access requires the separate `read:ops-config` scope. Alert listing uses `read:ops-alert`, so alert requests can succeed while schedule requests return an authorization error when the configuration or token lacks the schedule scope.

Yes, set `JSM_READ_ONLY=true` to withhold every write tool. The agent can still use the registered read capabilities, while acknowledgement, closure, annotation, and other write operations are not exposed.

Related MCP servers

All in Support & Service Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewJira Alerts (JSM Operations) AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/jira-alerts-jsm-operations?style=directory)](https://allmcps.com/mcp/jira-alerts-jsm-operations)
HTML Embed
<a href="https://allmcps.com/mcp/jira-alerts-jsm-operations"><img src="https://allmcps.com/api/badge/jira-alerts-jsm-operations?style=directory" alt="Jira Alerts (JSM Operations) on AllMCPs" /></a>