Jira Alerts (JSM Operations) — Claude Code MCP server
Jira Alerts (JSM Operations) is a Claude Code MCP server for finding Jira Service Management alerts and checking who is on call. Agents can acknowledge or close alerts, add notes, and assign responders.
Apache-2.0 ★ 7 updated 2026-11-17
claude mcp add --env JSM_CLOUD_ID=<JSM_CLOUD_ID> --env JSM_EMAIL=<JSM_EMAIL> --env JSM_API_TOKEN=<JSM_API_TOKEN> --env JSM_OAUTH_TOKEN=<JSM_OAUTH_TOKEN> --transport stdio jira-alerts-jsm-operations -- npx -y jira-alerts-mcpWhat Jira Alerts (JSM Operations) does
The server lets an agent search Jira Service Management Operations alerts and inspect their notes and activity history. It can also acknowledge or close an alert, attach a note, and add responders. It returns current and upcoming on-call information too.
Running it requires Node.js 24 or later, an Atlassian Cloud site with JSM Operations enabled, a cloud ID, an email address, and an Atlassian API token. Its setup also includes JSM_OAUTH_TOKEN. The package starts with npx -y jira-alerts-mcp; alert searches need the read:ops-alert scope, while schedule lookups require read:ops-config.
What it helps with
- find open Jira Service Management alerts
- read an alert’s notes and activity history
- acknowledge or close alerts through an agent
- check who is on call now and next
Example prompts for the agent
- List the open Jira Service Management alerts.
- Acknowledge the alert and add a note to it.
- Who is on call now, and who is next?
How to install Jira Alerts (JSM Operations)
Platform CLI
claude mcp add --env JSM_CLOUD_ID=<JSM_CLOUD_ID> --env JSM_EMAIL=<JSM_EMAIL> --env JSM_API_TOKEN=<JSM_API_TOKEN> --env JSM_OAUTH_TOKEN=<JSM_OAUTH_TOKEN> --transport stdio jira-alerts-jsm-operations -- npx -y jira-alerts-mcpReplace <…> with your own values
Platform CLI
codex mcp add jira-alerts-jsm-operations --env JSM_CLOUD_ID=<JSM_CLOUD_ID> --env JSM_EMAIL=<JSM_EMAIL> --env JSM_API_TOKEN=<JSM_API_TOKEN> --env JSM_OAUTH_TOKEN=<JSM_OAUTH_TOKEN> -- npx -y jira-alerts-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"jira-alerts-jsm-operations": {
"command": "npx",
"args": [
"-y",
"jira-alerts-mcp"
],
"env": {
"JSM_CLOUD_ID": "<JSM_CLOUD_ID>",
"JSM_EMAIL": "<JSM_EMAIL>",
"JSM_API_TOKEN": "<JSM_API_TOKEN>",
"JSM_OAUTH_TOKEN": "<JSM_OAUTH_TOKEN>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"jira-alerts-jsm-operations": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"jira-alerts-mcp"
],
"env": {
"JSM_CLOUD_ID": "<JSM_CLOUD_ID>",
"JSM_EMAIL": "<JSM_EMAIL>",
"JSM_API_TOKEN": "<JSM_API_TOKEN>",
"JSM_OAUTH_TOKEN": "<JSM_OAUTH_TOKEN>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e JSM_CLOUD_ID=<JSM_CLOUD_ID> -e JSM_EMAIL=<JSM_EMAIL> -e JSM_API_TOKEN=<JSM_API_TOKEN> -e JSM_OAUTH_TOKEN=<JSM_OAUTH_TOKEN> jira-alerts-jsm-operations npx -y jira-alerts-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Jira Alerts (JSM Operations)
How do I install Jira Alerts (JSM Operations) in Claude Code?
Run `claude mcp add jira-alerts-mcp -e JSM_CLOUD_ID=<JSM_CLOUD_ID> -e JSM_API_TOKEN=<JSM_API_TOKEN> -e JSM_OAUTH_TOKEN=<JSM_OAUTH_TOKEN> -- npx -y jira-alerts-mcp`. Node.js 24 or later and Atlassian credentials are required.
What does Jira Alerts (JSM Operations) do?
It gives an agent access to JSM Operations alerts for searching and inspection, lets it change alert status and add notes or responders, and provides on-call schedule details.
What does Jira Alerts (JSM Operations) need to run?
It needs Node.js 24 or later, an Atlassian Cloud site with JSM Operations enabled, a cloud ID, an email address, and an API token. The setup also includes JSM_OAUTH_TOKEN.