Skip to content
MCP server

Jira Alerts (JSM Operations)

Search and acknowledge Jira Service Management alerts and see who is on call

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI
Runs
Locally
Version
2.2.0
Listing updated
1 day ago

About Jira Alerts (JSM Operations)

Jira Alerts (JSM Operations) is an open-source MCP server for productivity. It runs locally on your machine and is started by your AI client.

Opsgenie's alerting moved into Jira Service Management Operations, and the author says no other Jira MCP server covers that surface. This one lets an assistant search alerts, read their notes and activity timeline, acknowledge or close them, add notes and responders, and look up who is on call now and next.

A demo in the README shows the agent confirming that an acknowledgement actually landed instead of assuming success, since the underlying writes are asynchronous. Tools are grouped into toolsets: the default responder set registers 28 tools, while JSM_TOOLSETS=all adds schedules, teams, maintenance windows and routing for 82. A read-only switch withholds every write tool.

It needs Node 24 or later, your Atlassian cloud ID and an API token or OAuth token, and runs over stdio or HTTP. A first check is asking for open alerts, which exercises jsm_list_alerts, then asking who is on call to try schedules, which needs a separate scope.

Install

Run in a terminal

claude mcp add jira-alerts-mcp --env JSM_CLOUD_ID='<JSM_CLOUD_ID>' --env JSM_API_TOKEN='<JSM_API_TOKEN>' --env JSM_OAUTH_TOKEN='<JSM_OAUTH_TOKEN>' -- npx -y jira-alerts-mcp

Add to claude_desktop_config.json

{
  "mcpServers": {
    "jira-alerts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "jira-alerts-mcp"
      ],
      "env": {
        "JSM_CLOUD_ID": "<JSM_CLOUD_ID>",
        "JSM_API_TOKEN": "<JSM_API_TOKEN>",
        "JSM_OAUTH_TOKEN": "<JSM_OAUTH_TOKEN>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "jira-alerts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "jira-alerts-mcp"
      ],
      "env": {
        "JSM_CLOUD_ID": "<JSM_CLOUD_ID>",
        "JSM_API_TOKEN": "<JSM_API_TOKEN>",
        "JSM_OAUTH_TOKEN": "<JSM_OAUTH_TOKEN>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "jira-alerts-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "jira-alerts-mcp"
      ],
      "env": {
        "JSM_CLOUD_ID": "<JSM_CLOUD_ID>",
        "JSM_API_TOKEN": "<JSM_API_TOKEN>",
        "JSM_OAUTH_TOKEN": "<JSM_OAUTH_TOKEN>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "jira-alerts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "jira-alerts-mcp"
      ],
      "env": {
        "JSM_CLOUD_ID": "<JSM_CLOUD_ID>",
        "JSM_API_TOKEN": "<JSM_API_TOKEN>",
        "JSM_OAUTH_TOKEN": "<JSM_OAUTH_TOKEN>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "jira-alerts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "jira-alerts-mcp"
      ],
      "env": {
        "JSM_CLOUD_ID": "<JSM_CLOUD_ID>",
        "JSM_API_TOKEN": "<JSM_API_TOKEN>",
        "JSM_OAUTH_TOKEN": "<JSM_OAUTH_TOKEN>"
      }
    }
  }
}

Configuration

  • JSM_CLOUD_IDAtlassian site cloud id (a UUID). Find it at https://<your-site>.atlassian.net/_edge/tenant_infoRequired
  • JSM_EMAILAtlassian account email, for API token auth. Required unless JSM_OAUTH_TOKEN is set.
  • JSM_API_TOKENAtlassian account API token, paired with JSM_EMAIL. Required unless JSM_OAUTH_TOKEN is set.
  • JSM_OAUTH_TOKENOAuth 3LO or Forge bearer token. Takes precedence over JSM_EMAIL and JSM_API_TOKEN.

Tools this server provides (2)

Taken from the project documentation; the running server may differ.

jsm_list_alerts
List alerts without needing ids.
jsm_list_schedules
List on-call schedules.

What it does

Alert search
Find open alerts and read notes and timelines.
Acknowledge and close
Write tools to acknowledge, close and annotate alerts.
On-call lookup
See who is on call now and next.
Toolset selection
Choose a narrow default or register all verified toolsets.
Read-only mode
One setting withholds every write tool.
Write confirmation
The agent checks that asynchronous writes landed.

Good for

  • Ask what is paging you right now
  • Acknowledge alerts you have already handled
  • Find the current on-call responder
  • Review an alert's activity timeline during an incident

Pricing

Open source

Free to run; needs your own Atlassian site

Jira Alerts (JSM Operations) FAQ

Which Jira product does it target?

Jira Service Management Operations, the alert surface that replaced Opsgenie.

What does it need?

Node 24 or later, your Atlassian cloud ID and an API token or OAuth token.

Can I stop it making changes?

Yes, set JSM_READ_ONLY to true.

Why does the schedules check fail with 401?

Schedules need a separate read:ops-config scope.

Is Jira Alerts (JSM Operations) free?

Yes. Jira Alerts (JSM Operations) is open source, so you can use and self-host it for free.

How do I add Jira Alerts (JSM Operations) to Claude Code?

Run this command in your terminal: claude mcp add jira-alerts-mcp --env JSM_CLOUD_ID='<JSM_CLOUD_ID>' --env JSM_API_TOKEN='<JSM_API_TOKEN>' --env JSM_OAUTH_TOKEN='<JSM_OAUTH_TOKEN>' -- npx -y jira-alerts-mcp

What are the best alternatives to Jira Alerts (JSM Operations)?

The closest alternatives to Jira Alerts (JSM Operations) are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

Alternatives to Jira Alerts (JSM Operations)

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  3. GitHub

    MCP server

    Official MCP server connecting AI assistants to GitHub repos, issues and workflows

    Not checked yet
    • Remote
    • Open source
    • 34.5K GitHub stars
    • Developer tools
  4. MCP toolkit giving coding agents symbol-level code retrieval and editing

    Runs locally
    • Open source
    • 31.5K GitHub stars
    • Developer tools
  5. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  6. Ha MCP

    MCP server

    MCP server for managing and automating Home Assistant from AI assistants

    Runs locally
    • 8 tools
    • Open source
    • 7.9K GitHub stars
    • Productivity