← Index

Jira Alerts (JSM Operations)

io.github.rrvrs/jira-alerts-mcpv1.0.3Productivity & Project Mgmt

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

The current version, v1.0.3, was published to the official MCP registry on 2026-08-22. It is distributed as jira-alerts-mcp on npm, filed under Productivity & Project Mgmt by this index, and declares 4 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Jira Alerts (JSM Operations) in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Auditable install path →Watch it hold a drift →
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-08-22).

Contracts can change after screening, with no version bump. The gate pins Jira Alerts (JSM Operations)’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
JSM_CLOUD_ID
required

Atlassian site cloud id (a UUID). Find it at https://<your-site>.atlassian.net/_edgeAuth/tenantInfo

JSM_EMAIL

Atlassian account email, for API token auth. Required unless JSM_OAUTH_TOKEN is set.

JSM_API_TOKEN
secret

Atlassian account API token, paired with JSM_EMAIL. Required unless JSM_OAUTH_TOKEN is set.

JSM_OAUTH_TOKEN
secret

OAuth 3LO or Forge bearer token. Takes precedence over JSM_EMAIL and JSM_API_TOKEN.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
10
Alternatives in Productivity & Project Mgmt
SmartCut
dev.smartcut/cutlist-optimizer

Cutlist optimization for sheet, linear and roll stock, with grain, kerf, nesting and saw exports.

Asana MCP Server
io.github.jtalk22/asana-mcp-server

Change Asana without opening Asana — custom fields, sections, start dates, rich notes, bulk. PAT.

io.github.ryudi84/gradient
io.github.ryudi84/gradient

MCP server for CSS gradient generation — linear, radial, conic