SERVER

Jira Alerts (JSM Operations)

Rank #3,931

io.github.rrvrs/jira-alerts-mcp

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

8 versions

4 GitHub stars

by rrvrs (1 servers)View repository ↗Claim this server

First listed

Aug 22, 2026

Last publish date

Sep 12, 2026

OVERVIEW

Jira Alerts (JSM Operations) is a Model Context Protocol (MCP) server published by rrvrs. It ranks #3,931 of 132,046 servers tracked on MCP Toplist, and its repository has 4 GitHub stars. Jira Alerts (JSM Operations) is listed across 2 registries — Official MCP and Glama, with 8 tracked versions. It was first listed on Aug 22, 2026 and most recently updated on Sep 12, 2026.

STANDING

#3,931of 132,046 tracked serversTop 5%

Ranks ahead of 128,115 of 132,046 servers on MCP Toplist.

CONNECT

Use Jira Alerts (JSM Operations)

API keyNeeds credentials

Requires user-supplied configuration before first use — typically an API key, token or connection string set via environment variables.

npm package

claude mcp add jira-alerts-mcp -e "JSM_CLOUD_ID=<your JSM_CLOUD_ID>" -e "JSM_EMAIL=<your JSM_EMAIL>" -e "JSM_API_TOKEN=<your JSM_API_TOKEN>" -e "JSM_OAUTH_TOKEN=<your JSM_OAUTH_TOKEN>" -- npx -y jira-alerts-mcp

Replace each placeholder with your own value before saving.

npm package

[mcp_servers.jira-alerts-mcp]
command = "npx"
args = ["-y", "jira-alerts-mcp"]

[mcp_servers.jira-alerts-mcp.env]
JSM_CLOUD_ID = "<your JSM_CLOUD_ID>"
JSM_EMAIL = "<your JSM_EMAIL>"
JSM_API_TOKEN = "<your JSM_API_TOKEN>"
JSM_OAUTH_TOKEN = "<your JSM_OAUTH_TOKEN>"

Add to ~/.codex/config.toml. Replace each placeholder with your own value before saving.

npm package

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

Add to claude_desktop_config.json (Settings → Developer → Edit Config). Replace each placeholder with your own value before saving.

npm package

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

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Replace each placeholder with your own value before saving.

npm package

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

Save as .vscode/mcp.json in your workspace. Replace each placeholder with your own value before saving.

npm package

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

Add to ~/.codeium/windsurf/mcp_config.json. Replace each placeholder with your own value before saving.

npm package

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

Replace each placeholder with your own value before saving.

BADGE

Show your rank

Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.

Markdown

[![MCP Toplist](https://mcptoplist.com/badge/io.github.rrvrs%2Fjira-alerts-mcp.svg)](https://mcptoplist.com/server/io.github.rrvrs%2Fjira-alerts-mcp)

HTML

<a href="https://mcptoplist.com/server/io.github.rrvrs%2Fjira-alerts-mcp"><img src="https://mcptoplist.com/badge/io.github.rrvrs%2Fjira-alerts-mcp.svg" alt="MCP Toplist: Top 5% of 132,046" /></a>

Variants: append ?metric=score or ?metric=stars to the image URL.

REGISTRIES

Listed on 2 registries

Official MCP

Glama

ORGANIZATION

rrvrs

Organization

rrvrs

Servers in org

Versions across org

VERSIONS

Available versions (8)

Version	Published
2.1.0	Sep 12, 2026
2.0.1	Sep 12, 2026
2.0.0	Sep 6, 2026
1.1.1	Aug 26, 2026
1.1.0	Aug 23, 2026
1.0.4	Aug 22, 2026
1.0.3	Aug 22, 2026
1.0.1	Aug 22, 2026

FAQ

Frequently asked questions

Who maintains Jira Alerts (JSM Operations)?: Jira Alerts (JSM Operations) is maintained by rrvrs, which publishes 1 MCP server (8 total versions) tracked on MCP Toplist.
Is Jira Alerts (JSM Operations) listed on the Official MCP Registry?: Yes — Jira Alerts (JSM Operations) is listed on the Official MCP Registry, alongside Glama.
How many versions does Jira Alerts (JSM Operations) have?: MCP Toplist tracks 8 versions of Jira Alerts (JSM Operations), most recently published on Sep 12, 2026.
Where can I find the source code for Jira Alerts (JSM Operations)?: The source code for Jira Alerts (JSM Operations) is hosted at github.com/rrvrs/jira-alerts-mcp.

Used in projects

Do you run this server?

Add to a project

Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.

EXPLORE

All MCP Servers Official MCP Servers GitHub MCP Servers Best MCP Servers Most Active MCP Servers New MCP Servers Best New MCP Servers