Jira Alerts (JSM Operations) MCP Server

Find what is paging you, and who is on call - from your agent. An MCP server for Jira Service Management Operations - the alert surface that replaced Opsgenie, which no other Jira MCP server covers. Its 13 documented tools cover jsm, alert. It runs locally over stdio via the published package.

People connecting productivity tools to Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-08-23 · ★ 2 · #41 OF 139 MAINTAINED PRODUCTIVITY · VERIFIED 2026-08-25

Apache-2.0 · TypeScript servers · how we verify → /methodology

01 · Install Jira Alerts (JSM Operations)

before you install - you'll need

Set JSM_CLOUD_ID, JSM_EMAIL, JSM_API_TOKEN before connecting.

Claude Code

claude mcp add rrvrs-jira-alerts-mcp -- npx -y jira-alerts-mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "rrvrs-jira-alerts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "jira-alerts-mcp"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

repo age created 2026-08-21 - young repo, little track record yet

license Apache-2.0 - declared in the repository

npm package jira-alerts-mcp - unscoped; check the name against the project README before installing

registry namespace io.github.rrvrs is GitHub-verified and matches the repo owner

03 · What Jira Alerts (JSM Operations) can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

With this server connected, an agent can get /v1/alerts, get /v1/alerts/{id} or get /v1/alerts/alias, get /v1/alerts/{id}/notes, and get /v1/alerts/{id}/logs.

The 13 tools it gives your agent

Extracted from the project's README - what Jira Alerts (JSM Operations) lets an agent do.

jsm_list_alerts: - GET /v1/alerts
jsm_get_alert: - GET /v1/alerts/{id} or GET /v1/alerts/alias
jsm_list_alert_notes: - GET /v1/alerts/{id}/notes
jsm_list_alert_logs: - GET /v1/alerts/{id}/logs
jsm_get_request_status: - GET /v1/alerts/requests/{id}
jsm_acknowledge_alert: - POST /v1/alerts/{id}/acknowledge
jsm_close_alert: - POST /v1/alerts/{id}/close
jsm_add_alert_note: - POST /v1/alerts/{id}/notes
jsm_add_alert_responder: - POST /v1/alerts/{id}/responders
jsm_list_schedules: - GET /v1/schedules
jsm_get_on_call: - GET /v1/schedules/{id}/on-calls
jsm_get_next_on_call: - GET /v1/schedules/{id}/next-on-calls

show all 13 tools

jsm_get_schedule_timeline: - GET /v1/schedules/{id}/timeline

Latest releases

v1.1.0 · 2026-08-23

Fixes · Read the field names the JSM Operations API actually sends

v1.0.5 · 2026-08-22

Other changes · Document connecting from Claude Desktop · Point at the real tenant_info endpoint, and release 1.0.5

v1.0.4 · 2026-08-22

Other changes · Correct the scope documentation, and the 401 that hid the problem · Release 1.0.4

04 · Who maintains Jira Alerts (JSM Operations)

Jira Alerts (JSM Operations) is maintained by rrvrs. It's the only MCP server we track from this author; the repo dates to Aug 2026.

05 · Facts

repository: github.com/rrvrs/jira-alerts-mcp
website: https://github.com/rrvrs/jira-alerts-mcp#readme
category: productivity - ranked #41 of 139 actively-maintained productivity servers as of 2026-08-25.
release cadence: 7 releases in the last 90 days (latest 2026-08-23)
registry: io.github.rrvrs/jira-alerts-mcp (active, first published 2026-08-22 · 4 versions)
packages: npm:jira-alerts-mcp

06 · Jira Alerts (JSM Operations) FAQ

Is Jira Alerts (JSM Operations) still maintained?

Yes - as of 2026-08-25, its last commit was 2026-08-23 and it shipped 7 releases in the last 90 days. We re-verify nightly.

What can Jira Alerts (JSM Operations) do?

With this server connected, an agent can get /v1/alerts, get /v1/alerts/{id} or get /v1/alerts/alias, get /v1/alerts/{id}/notes, and get /v1/alerts/{id}/logs.

How do I install Jira Alerts (JSM Operations)?

Run `npx -y jira-alerts-mcp`. The README documents 3 environment variables (JSM_CLOUD_ID, JSM_EMAIL, JSM_API_TOKEN) to set first. Set JSM_CLOUD_ID, JSM_EMAIL, JSM_API_TOKEN before connecting. You can also paste the ready-made client config above.

Does Jira Alerts (JSM Operations) run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Jira Alerts (JSM Operations)

Alternatives to Jira Alerts (JSM Operations)

Maintained productivity servers if Jira Alerts (JSM Operations) isn't the fit.

Pairs well with

Servers that cover what Jira Alerts (JSM Operations) doesn't - only shown when the pairing reason fits the companion.

More productivity MCP servers · Frappe Dev MCP Server · LINZA · Nouz · SAME - Stateless Agent Memory Engine · Seekstone

More TypeScript MCP servers · Janee · Rootstock (RSK) MCP Server · Guardian · Runapi MCP · Browser Agent · see all