
Jira Alerts (JSM Operations) MCP Server
by rrvrsio.github.rrvrs/jira-alerts-mcpv2.1.0
MCP server for Jira Service Management Operations — alerts, on-call schedules and responders
context tax
queued
security
queued
cold start
queued
freshness
Active28d ago
Install Jira Alerts (JSM Operations) MCP server
Install in Claude Code
claude mcp add jira-alerts -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-mcpInstall in Cursor
{
"mcpServers": {
"jira-alerts": {
"command": "npx",
"args": [
"-y",
"jira-alerts-mcp"
],
"env": {
"JSM_CLOUD_ID": "<jsm-cloud-id>",
"JSM_API_TOKEN": "<jsm-api-token>",
"JSM_OAUTH_TOKEN": "<jsm-oauth-token>"
}
}
}
}Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
Install in Claude Desktop
{
"mcpServers": {
"jira-alerts": {
"command": "npx",
"args": [
"-y",
"jira-alerts-mcp"
],
"env": {
"JSM_CLOUD_ID": "<jsm-cloud-id>",
"JSM_API_TOKEN": "<jsm-api-token>",
"JSM_OAUTH_TOKEN": "<jsm-oauth-token>"
}
}
}
}Settings → Developer → Edit Config (claude_desktop_config.json), then restart.
Install in VS Code
{
"servers": {
"jira-alerts": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"jira-alerts-mcp"
],
"env": {
"JSM_CLOUD_ID": "<jsm-cloud-id>",
"JSM_API_TOKEN": "<jsm-api-token>",
"JSM_OAUTH_TOKEN": "<jsm-oauth-token>"
}
}
}
}Add to .vscode/mcp.json in your workspace.
Install in Windsurf
{
"mcpServers": {
"jira-alerts": {
"command": "npx",
"args": [
"-y",
"jira-alerts-mcp"
],
"env": {
"JSM_CLOUD_ID": "<jsm-cloud-id>",
"JSM_API_TOKEN": "<jsm-api-token>",
"JSM_OAUTH_TOKEN": "<jsm-oauth-token>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json.
Configuration
| Variable | Required | Secret | Description |
|---|---|---|---|
| JSM_CLOUD_ID | yes | — | 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 | — | yes | Atlassian account API token, paired with JSM_EMAIL. Required unless JSM_OAUTH_TOKEN is set. |
| JSM_OAUTH_TOKEN | — | yes | OAuth 3LO or Forge bearer token. Takes precedence over JSM_EMAIL and JSM_API_TOKEN. |
Freshness
Active — last maintenance signal 28d ago. The newest of the signals below sets the band.
Last commit (default branch)
2026-09-12 · 28d ago · GitHub
Latest release
2026-09-12 · 28d ago · GitHub · v2.1.0
Package published
no data · npm/PyPI
Registry entry updated
2026-09-12 · 28d ago · official registry · v2.1.0
FAQ
›How do I install the Jira Alerts (JSM Operations) MCP server in Claude Code?
Run: claude mcp add jira-alerts -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. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.
›Does Jira Alerts (JSM Operations) require an API key?
Yes. It expects JSM_CLOUD_ID, JSM_API_TOKEN, JSM_OAUTH_TOKEN, of which 2 are secrets.
›Can I use Jira Alerts (JSM Operations) as a remote (hosted) MCP server?
No hosted endpoint is published; it runs locally over stdio.
›Is Jira Alerts (JSM Operations) in the official MCP registry?
Yes, as io.github.rrvrs/jira-alerts-mcp.
Alternatives to Jira Alerts (JSM Operations)
Other project management MCP servers.