Jira Alerts (JSM Operations) MCP server

Read from the package source without running it. The installed server may list more.

• jsm_delete_contactwrite action

  Permanently remove a contact method from an account. Args: - contact_id (string) Returns: { "deleted": true, "contact_id": string } If this is the account's only contact method, that person can no longer be notified by anything — check with jsm_list_contacts first. jsm_deactivate_contact is the reversible way to stop delivery. Requires delete:ops-config:jira-service-management. That grant belongs

• jsm_delete_maintenancewrite action

  Permanently delete a maintenance window. Args: - maintenance_id (string), team_id (string, optional) Returns: { "deleted": true, "maintenance_id": string } Deleting an active window resumes alerting immediately for everything it silenced. If the goal is to end it early, jsm_cancel_maintenance does that and keeps the record of what was silenced and when. Requires delete:ops-config:jira-service-mana

• jsm_delete_routing_rulewrite action

  Delete a routing rule. Args: - team_id (string), routing_rule_id (string) Returns: { "deleted": true, "routing_rule_id": string } Alerts that matched this rule fall through to the next one, which may route them somewhere else entirely or nowhere at all. Read the full list first so you can say where they will go instead. Requires delete:ops-config:jira-service-management. That grant belongs to the

• jsm_update_contactwrite action

  Change where a contact method delivers. Args: - contact_id (string): the method to change - to (string): the new address or number Returns: { "contact": { "id": string, ... } } Only the destination can be changed — the method itself ('email', 'sms', 'voice') is fixed at creation, so switching someone from SMS to email means creating a new contact and deleting the old one. Changing the destination

• jsm_update_maintenancewrite action

  Change a maintenance window's description, period or rules. Args: - maintenance_id (string), team_id (string, optional) - description, start_date, end_date, rules Returns: { "maintenance": { "id": string, ... } } IMPORTANT: `rules` replaces the whole list. Extending a window's end date keeps alerting suppressed for longer — say so when reporting back, because it is the opposite of what "update" us

• jsm_update_routing_rulewrite action

  Change a routing rule's name, target, order or timezone. Args: - team_id (string), routing_rule_id (string) - name, order, notify_type, notify_id, timezone Returns: { "routing_rule": { "id": string, ... } } THIS CHANGES WHO GETS PAGED, immediately and for every matching alert. Setting notify_type='none' makes matching alerts route nowhere at all. To move a rule up or down the list, prefer jsm_chan

• Code scan153 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 6 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Jira Alerts (JSM Operations): common questions

Is Jira Alerts (JSM Operations) MCP server safe?

Mostly: it is graded B (83/100). Read the Jira Alerts (JSM Operations) safety report

How do I install Jira Alerts (JSM Operations)?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does Jira Alerts (JSM Operations) need an API key?

Yes. The registry entry asks for JSM_API_TOKEN, JSM_OAUTH_TOKEN.

Is Jira Alerts (JSM Operations) maintained?

The last commit was 6 days ago (2026-09-14). The latest release is v2.1.0.

What can I use instead of Jira Alerts (JSM Operations)?

Servers from other publishers that do the same job: Alces MCP server, Atlassian Rovo MCP Server and Radar Kubernetes MCP Server. Compare all Jira Alerts (JSM Operations) alternatives.