MCP Hub › Developer Tools › Jira Alerts (JSM Operations)

Jira Alerts (JSM Operations) MCP server

by rrvrs · io.github.rrvrs/jira-alerts-mcp

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

🛠 Developer Toolsnpmv2.1.1
Open in MCP HubGitHub repository ↗Website ↗

How to install Jira Alerts (JSM Operations)

npm

claude mcp add -e JSM_CLOUD_ID=<your-jsm-cloud-id> jira-alerts-mcp -- npx -y [email protected]

Or add it to your MCP config (Claude Desktop, Cursor, VS Code):

{
  "mcpServers": {
    "jira-alerts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "JSM_CLOUD_ID": "<your-jsm-cloud-id>"
      }
    }
  }
}

Environment variables:
JSM_CLOUD_ID (required) – Atlassian site cloud id (a UUID). Find it at https://<your-site>.atlassian.net/_edge/tenant_info
JSM_EMAIL – Atlassian account email, for API token auth. Required unless JSM_OAUTH_TOKEN is set.
JSM_API_TOKEN – Atlassian account API token, paired with JSM_EMAIL. Required unless JSM_OAUTH_TOKEN is set.
JSM_OAUTH_TOKEN – OAuth 3LO or Forge bearer token. Takes precedence over JSM_EMAIL and JSM_API_TOKEN.

Replace placeholders in <angle brackets> with your own values. Review what a server can access before you enable it.

Details

Version
2.1.1
Published
2026-10-24
Updated
2026-10-24
Namespace
io.github.rrvrs
Source
rrvrs/jira-alerts-mcp

Similar developer tools servers