What it does
MCP server for Jira Service Management Operations — alerts, on-call schedules and responders
- Connects Runs on your computer
- Account or key Needs JSM_API_TOKEN, JSM_OAUTH_TOKEN · 2 settings to fill in (JSM_CLOUD_ID, JSM_EMAIL)
- Category Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 9/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 21/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Jira Alerts (JSM Operations). Follow https://mcp.popnx.com/i/rrvrs-jira-alerts-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 17, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a Jira Alerts (JSM Operations) key (create it on the maker’s site) · 2 setting(s) to fill in (JSM_CLOUD_ID, JSM_EMAIL) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Let AI install it
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Jira Alerts (JSM Operations) for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "jira-alerts": { "command": "npx", "args": [ "-y", "jira-alerts-mcp" ], "env": { "JSM_CLOUD_ID": "your-value", "JSM_EMAIL": "your-value", "JSM_API_TOKEN": "your-value", "JSM_OAUTH_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For JSM_API_TOKEN, JSM_OAUTH_TOKEN, JSM_CLOUD_ID, JSM_EMAIL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Jira Alerts (JSM Operations) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
node -vInstall once; it works for everything that needs Node.js
Sign up and create a Jira Alerts (JSM Operations) key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Fill in 2 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
JSM_CLOUD_IDAtlassian site cloud id (a UUID). Find it at https:// .atlassian.net/_edge/tenant_infoJSM_EMAILAtlassian account email, for API token auth. Required unless JSM_OAUTH_TOKEN is set.
Descriptions are as written by the maker.
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Paste these settings and save the file
{ "mcpServers": { "jira-alerts": { "command": "npx", "args": [ "-y", "jira-alerts-mcp" ], "env": { "JSM_CLOUD_ID": "your-value", "JSM_EMAIL": "your-value", "JSM_API_TOKEN": "your-value", "JSM_OAUTH_TOKEN": "your-value" } } } }Paste the key only into the app’s field, never into a chat or to anyone
Quit Claude and open it again
Try it
Use Jira Alerts (JSM Operations) and tell me what you can do for me, then show me one thing✓ If Claude says it is using Jira Alerts (JSM Operations) or shows a Jira Alerts (JSM Operations) tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Jira Alerts (JSM Operations) yet
Jira Alerts (JSM Operations) runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect Jira Alerts (JSM Operations)
- You need a Jira Alerts (JSM Operations) key (create it on the maker’s site) · 2 setting(s) to fill in (JSM_CLOUD_ID, JSM_EMAIL) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
- You need a Jira Alerts (JSM Operations) key (create it on the maker’s site) · 2 setting(s) to fill in (JSM_CLOUD_ID, JSM_EMAIL) · Install Node.js on your computer first (one time)
- You need a Jira Alerts (JSM Operations) key (create it on the maker’s site) · 2 setting(s) to fill in (JSM_CLOUD_ID, JSM_EMAIL) · Install Node.js on your computer first (one time)
- You need a Jira Alerts (JSM Operations) key (create it on the maker’s site) · 2 setting(s) to fill in (JSM_CLOUD_ID, JSM_EMAIL) · Install Node.js on your computer first (one time)
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Works with Claude Code, with some setup first
You need a Jira Alerts (JSM Operations) key (create it on the maker’s site) · 2 setting(s) to fill in (JSM_CLOUD_ID, JSM_EMAIL) · Install Node.js on your computer first (one time)
Let AI install it
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Jira Alerts (JSM Operations) for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user jira-alerts --env JSM_CLOUD_ID=your-value --env JSM_EMAIL=your-value --env JSM_API_TOKEN=your-value --env JSM_OAUTH_TOKEN=your-value -- npx -y jira-alerts-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For JSM_API_TOKEN, JSM_OAUTH_TOKEN, JSM_CLOUD_ID, JSM_EMAIL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Jira Alerts (JSM Operations) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
node -vInstall once; it works for everything that needs Node.js
Sign up and create a Jira Alerts (JSM Operations) key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Fill in 2 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
JSM_CLOUD_IDAtlassian site cloud id (a UUID). Find it at https:// .atlassian.net/_edge/tenant_infoJSM_EMAILAtlassian account email, for API token auth. Required unless JSM_OAUTH_TOKEN is set.
Descriptions are as written by the maker.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --scope user jira-alerts --env JSM_CLOUD_ID=your-value --env JSM_EMAIL=your-value --env JSM_API_TOKEN=your-value --env JSM_OAUTH_TOKEN=your-value -- npx -y jira-alerts-mcpReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
Type /mcp in Claude Code
You should see Jira Alerts (JSM Operations) listed as connected
Try it
Use Jira Alerts (JSM Operations) and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Jira Alerts (JSM Operations) or shows a Jira Alerts (JSM Operations) tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Jira Alerts (JSM Operations) key (create it on the maker’s site) · 2 setting(s) to fill in (JSM_CLOUD_ID, JSM_EMAIL) · Install Node.js on your computer first (one time)
Let AI install it
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Jira Alerts (JSM Operations) for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "jira-alerts": { "command": "npx", "args": [ "-y", "jira-alerts-mcp" ], "env": { "JSM_CLOUD_ID": "your-value", "JSM_EMAIL": "your-value", "JSM_API_TOKEN": "your-value", "JSM_OAUTH_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For JSM_API_TOKEN, JSM_OAUTH_TOKEN, JSM_CLOUD_ID, JSM_EMAIL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Jira Alerts (JSM Operations) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
node -vInstall once; it works for everything that needs Node.js
Sign up and create a Jira Alerts (JSM Operations) key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Fill in 2 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
JSM_CLOUD_IDAtlassian site cloud id (a UUID). Find it at https:// .atlassian.net/_edge/tenant_infoJSM_EMAILAtlassian account email, for API token auth. Required unless JSM_OAUTH_TOKEN is set.
Descriptions are as written by the maker.
Fill in your key
In the Jira Alerts (JSM Operations) settings, JSM_API_TOKEN, JSM_OAUTH_TOKEN, JSM_CLOUD_ID, JSM_EMAIL is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Open the AI chat in Cursor in Agent mode
Try it
Use Jira Alerts (JSM Operations) and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Jira Alerts (JSM Operations) or shows a Jira Alerts (JSM Operations) tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Jira Alerts (JSM Operations) key (create it on the maker’s site) · 2 setting(s) to fill in (JSM_CLOUD_ID, JSM_EMAIL) · Install Node.js on your computer first (one time)
Let AI install it
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Jira Alerts (JSM Operations) for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "jira-alerts": { "type": "stdio", "command": "npx", "args": [ "-y", "jira-alerts-mcp" ], "env": { "JSM_CLOUD_ID": "your-value", "JSM_EMAIL": "your-value", "JSM_API_TOKEN": "your-value", "JSM_OAUTH_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For JSM_API_TOKEN, JSM_OAUTH_TOKEN, JSM_CLOUD_ID, JSM_EMAIL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Jira Alerts (JSM Operations) tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
node -vInstall once; it works for everything that needs Node.js
Sign up and create a Jira Alerts (JSM Operations) key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Fill in 2 setting(s)
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
JSM_CLOUD_IDAtlassian site cloud id (a UUID). Find it at https:// .atlassian.net/_edge/tenant_infoJSM_EMAILAtlassian account email, for API token auth. Required unless JSM_OAUTH_TOKEN is set.
Descriptions are as written by the maker.
Fill in your key
In the Jira Alerts (JSM Operations) settings, JSM_API_TOKEN, JSM_OAUTH_TOKEN, JSM_CLOUD_ID, JSM_EMAIL is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Open the AI chat in VS Code in Agent mode
Try it
Use Jira Alerts (JSM Operations) and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Jira Alerts (JSM Operations) or shows a Jira Alerts (JSM Operations) tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
For developers: Terminal commands and JSON settings
Installed on your computer
Claude Code
claude mcp add --scope user jira-alerts --env JSM_CLOUD_ID=your-value --env JSM_EMAIL=your-value --env JSM_API_TOKEN=your-value --env JSM_OAUTH_TOKEN=your-value -- npx -y jira-alerts-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"jira-alerts": {
"command": "npx",
"args": [
"-y",
"jira-alerts-mcp"
],
"env": {
"JSM_CLOUD_ID": "your-value",
"JSM_EMAIL": "your-value",
"JSM_API_TOKEN": "your-value",
"JSM_OAUTH_TOKEN": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"jira-alerts": {
"command": "npx",
"args": [
"-y",
"jira-alerts-mcp"
],
"env": {
"JSM_CLOUD_ID": "your-value",
"JSM_EMAIL": "your-value",
"JSM_API_TOKEN": "your-value",
"JSM_OAUTH_TOKEN": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"jira-alerts": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"jira-alerts-mcp"
],
"env": {
"JSM_CLOUD_ID": "your-value",
"JSM_EMAIL": "your-value",
"JSM_API_TOKEN": "your-value",
"JSM_OAUTH_TOKEN": "your-value"
}
}
}
}Values you fill in
JSM_CLOUD_IDrequired envAtlassian site cloud id (a UUID). Find it at https:// .atlassian.net/_edge/tenant_infoJSM_EMAILrequired envAtlassian account email, for API token auth. Required unless JSM_OAUTH_TOKEN is set.JSM_API_TOKENsecret required envAtlassian account API token, paired with JSM_EMAIL. Required unless JSM_OAUTH_TOKEN is set.JSM_OAUTH_TOKENsecret required envOAuth 3LO or Forge bearer token. Takes precedence over JSM_EMAIL and JSM_API_TOKEN.
Descriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
- Downloads per weeki
- 102/wk
- Connection
- Runs on your computer
- Latest versioni
- 2.2.1
- Categoryi
- Developer tools
- Published to registryi
- Nov 17, 2026
- Code last changedi
- Nov 17, 2026
- Maker
- rrvrs
- Packages
npm: jira-alerts-mcp- Website
- github.com
- Registry status
- Active
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account rrvrs, which owns the repo
- ✓ Pass
Still maintained
Code last changed 2 days ago
- ✓ Pass
Has a licence
Uses Apache-2.0
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Published vulnerabilities (OSV.dev)
Not checked yet
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/rrvrs-jira-alerts-mcp)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 85% of the other 6136 servers in this category
- Published to the registry more recently than 95% of the other 6136 servers in this category
- Basic checks equal to or better than 99% of the other 6136 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Jira Alerts (JSM Operations) safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: JSM_API_TOKEN, JSM_OAUTH_TOKEN
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed 2 days ago, and the latest version (2.2.1) reached the registry 2 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP
Cloudflare MCP servers
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Jira Alerts (JSM Operations) | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | Apache-2.0 | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Jira Alerts MCP
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.
Search alerts and read their notes and activity timeline; acknowledge, close, annotate them and add responders; and look up who is on call now and next. Twelve tools, four of them writes.
Demo
Three questions in one session, against a live JSM site: who is on call, what is open, and acknowledge what isn't. Watch the last answer in particular — the agent confirms the acknowledgement actually landed (ack landed 16:38:00.577Z) instead of assuming it did, which is the asynchronous-write behaviour described under What this server handles for you.
Quickstart
You need Node ≥ 24 and an Atlassian Cloud site with JSM Operations enabled. There is nothing to clone or build — your MCP client runs the published package.
1. Find your cloud id. Open this while logged in to your site:
https://<your-site>.atlassian.net/_edge/tenant_info
It answers with one line — {"cloudId":"..."} — and that UUID is what JSM_CLOUD_ID wants. If you'd rather not rely on that endpoint, the cloud id is also the segment after /s/ in the URL at admin.atlassian.com → Apps → Sites → your site.
2. Create an API token at id.atlassian.com.
3. Add the server.
*Claude Code:*
claude mcp add jira-alerts-mcp \
--scope user \ --env JSM_CLOUD_ID='your-cloud-id' \ --env JSM_EMAIL='you@example.com' \ --env JSM_API_TOKEN="${JSM_API_TOKEN}" \ --env JSM_TOOLSETS='all' \ -- npx -y jira-alerts-mcp
JSM_TOOLSETS=all registers every verified toolset — 82 tools rather than the 28 the responder default gives you, adding schedules, teams, maintenance windows and routing. Drop the line to start narrow; all is not the widest possible surface, because the three quarantined families still have to be asked for by name. See Choosing your toolsets for what each one covers and why a bigger tool list is not automatically better.
--scope user registers the server for your whole account rather than only the directory you happened to run the command in. That is what you want for an alerts server — you want it in every session. Without the flag claude mcp add defaults to local scope, and the server exists in that one directory only.
*Claude Desktop:* open the config from the app rather than by hand — the Claude menu in your menu bar (not the settings inside the window) → Settings → Developer → Edit Config. That creates the file if it doesn't exist yet:
| OS | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
{
"mcpServers": { "jira-alerts-mcp": { "command": "npx", "args": ["-y", "jira-alerts-mcp"], "env": { "JSM_CLOUD_ID": "your-cloud-id", "JSM_EMAIL": "you@example.com", "JSM_API_TOKEN": "your-api-token", "JSM_TOOLSETS": "all" } } } }
mcpServers is a top-level key, and the file holds every server you have configured. If it already has an mcpServers block, add jira-alerts-mcp as another entry inside it — pasting the whole block above over the file replaces whatever was already there.
Then quit Claude Desktop completely and reopen it — the file is read only at startup, and closing the window is not quitting. The server then appears under the connectors panel in the message composer.
Most other MCP clients accept that same JSON shape. There is no scope choice to make here — claude_desktop_config.json is already per-user, the same reach as --scope user on the CLI.
4. Check it works. Ask your agent to list your open alerts. That runs jsm_list_alerts, which needs no ids and confirms your credentials and the read:ops-alert scope that nine of the fourteen tools share.
Then ask who is on call, which runs jsm_list_schedules. That is a separate check, because schedules need read:ops-config — if alerts work and schedules return 401, nothing is wrong with your token; see Required scopes below.
Things that catch people out: with claude mcp add the server name is the first positional argument, before any flags; -y on npx skips the install prompt, which an MCP client has no way to answer; and in zsh ${VAR} needs quoting. A server added without --scope user works in the directory you added it from and is simply missing everywhere else, with no error to explain the absence — if it seems to have disappeared, run claude mcp list from a different directory before touching anything else. For GUI-launched sessions the token has to live in the env block of the config itself — the shell environment isn't inherited, which is why the JSON above carries the credentials inline.
If the server never shows up in Claude Desktop, two causes account for almost all of it, and neither announces itself:
- `npx` wasn't on the PATH. A GUI app is launched by the window manager, not a shell, so a Node installed through nvm often isn't visible to it. Set
"command"to the absolute path fromwhich nodeand point"args"at the installeddist/index.js, or install Node system-wide. A Node older than 24 that *is* found fails asEBADENGINErather than anything readable. - The server exited during startup. Credentials are validated before the handshake, so a bad cloud id or token stops it dead — and because stdout is the protocol channel, that message goes to stderr only. Claude Desktop keeps it at
~/Library/Logs/Claude/mcp-server-jira-alerts-mcp.log(Windows:%APPDATA%\Claude\logs\), named after the key you used undermcpServers. Look forStartup failed:— it names exactly what is wrong.
Came here from this repository's Packages panel?
You found @rrvrs/jira-alerts-mcp on GitHub Packages. That is a mirror of the same build, published so the panel is not empty. GitHub Packages requires a personal access token even for public packages, so installing from it needs auth that npmjs.com does not.
Use npx jira-alerts-mcp above — that is the package on npmjs.com, installable anonymously, and the only supported install route. The two are separate names on separate registries; nothing redirects between them.
Running from a clone instead
Only needed to work on the server itself, or to run a revision that has not been released:
git clone https://github.com/rrvrs/jira-alerts-mcp.git
cd jira-alerts-mcp npm install npm run build
Then point your client at the build rather than at npx, so edits take effect without republishing:
-- node /absolute/path/to/jira-alerts-mcp/dist/index.js
Configuration
| Variable | Required | Notes |
|---|---|---|
JSM_CLOUD_ID | yes | Your Atlassian site's cloud id (a UUID) |
JSM_EMAIL + JSM_API_TOKEN | one of | Create a token |
JSM_OAUTH_TOKEN | one of | OAuth 3LO bearer; takes precedence if set |
JSM_TOOLSETS | no | Which tool families to register — see Choosing your toolsets. Unset registers responder |
JSM_READ_ONLY | no | true withholds every write tool |
TRANSPORT | no | stdio (default) or http |
PORT / HOST | no | HTTP transport; defaults to 127.0.0.1:3000 |
ALLOWED_HOSTS | no | Comma-separated Host allowlist. Required if you set HOST beyond loopback — see SECURITY.md |
Credentials are validated at startup, so a bad config fails immediately with an actionable message rather than on the first tool call.
.env.example lists these for reference. The server does not read .env itself — an MCP server is launched by its client, and the client owns the environment. Use the file as a checklist for your client's env block, or set -a; source .env; set +a for local development.
What your credentials can and cannot do
Both auth methods are not equivalent, and the difference is not documented by Atlassian. Verified against a live tenant on 2026-09-05:
The delete scopes are granted per token, not per authentication method. Two Atlassian account API tokens for the same account behave differently: one was refused on every DELETE with 401 Unauthorized; scope does not match — valid credentials, missing grant — and another completed the whole set. So a 401 on a delete is not a reason to abandon JSM_EMAIL + JSM_API_TOKEN. Reissue the token with the delete scopes included, or supply a 3LO or Forge OAuth token granted delete:ops-alert:jira-service-management as JSM_OAUTH_TOKEN. The 401 handler says exactly this, so the model reports it rather than retrying.
The delete-backed alert tools are jsm_delete_alert · jsm_delete_alert_note · jsm_remove_alert_tags · jsm_remove_alert_extra_properties · jsm_delete_alert_attachment.
The alert attachment endpoints are gated twice over. The API's own OpenAPI document maps them to no OAuth scope at all, so a token missing the delete scopes is turned away at the gateway with the same bare scope does not match — which reads like an auth dead end and is not one. A fully scoped token reaches the API and is told Feature not available in your plan instead. On a site whose plan excludes attachments, no token opens them, which is why they now live in their own quarantined attachments toolset that no profile loads. The handler reports the plan limit as a plan limit rather than sending you off to widen a token.
Some actions depend on your JSM plan, not on your scopes. On a Standard tenant, snooze, assign and custom actions are accepted and then fail out of band with Your account plan does not support …. The request is well-formed; the plan is the limit. This is exactly why writes are asynchronous and why jsm_get_request_status matters — the immediate response to all three is a successful receipt.
What has and has not been verified
Every tool in this server was run against a live Jira Service Management site before release. Every tool that a profile can load returned a real success — that is an invariant, and a test enforces it: a toolset marked unverified cannot appear in a profile.
Three families could not be verified, and they ship quarantined rather than removed. Nothing about them is known to be broken; they were untestable on the site available, and the code is very likely correct for a site where they are not blocked.
| Toolset | What the API answered | What that means |
|---|
| heartbeats | `402 Please upgrade