MCP Tools Directory
← Browse integrations

Developer tools

Jira Alerts (JSM Operations)

Free account · sign-in required

Contact Jira Alerts (JSM Operations)

Loading secure sign-in…

Tools for autonomous AI agents

Official website ↗

About this integration

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

Transport
stdio
Authentication
api-key
Initial setup
credentials
Runtime
unattended
Evidence
documented
Version
2.1.0
Package
jira-alerts-mcp
Last compatibility test
Not independently tested

Connect your agent

jira-alerts-mcp

Publisher README and npm manifest reviewed from pinned captures. The package, Atlassian tenant, provider API, and tools were not executed or independently security-audited by this directory review. The publisher documents mutating tools, plan-dependent capabilities, and quarantined tool families; consumers should scope credentials and toolsets deliberately.

Repository ↗Authentication & capability evidence ↗

Capabilities: Search and inspect Jira Service Management Operations alerts, Acknowledge, close, annotate, and route alerts, Read on-call schedules and timelines, Manage selected schedules, teams, maintenance, and routing resources

Connected profiles

Developer toolsindustries

Additional details

Registry identifier

io.github.rrvrs/jira-alerts-mcp

Source ↗ · Checked 2026-09-17
Published version

2.1.0

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Required configuration names

JSM_CLOUD_ID

Source ↗ · Checked 2026-09-17
Source artifact

jira-alerts-mcp

Source ↗ · Checked 2026-09-19
Source manifest version

2.1.0

Source ↗ · Checked 2026-09-19
Unattended configuration

The publisher documents an MCP server launched and supervised by the client, with startup credential validation and stdio as the default transport. This directory review did not start it.

Source ↗ · Checked 2026-09-19
Authentication and prerequisites

The documented primary setup uses an Atlassian account email plus JSM_API_TOKEN and JSM_CLOUD_ID. JSM_OAUTH_TOKEN is an alternative OAuth 3LO bearer that takes precedence when supplied; provider scopes and plan access constrain operations.

Source ↗ · Checked 2026-09-19
Connection configuration

The MCP client launches jira-alerts-mcp with npx over stdio by default. The package also documents an optional HTTP transport, but the existing stdio identity and null endpoint are preserved.

Source ↗ · Checked 2026-09-19
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-19