A
licenseNot graded
qualityD
maintenanceEnables comprehensive Opsgenie alert management including listing, creating, acknowledging, and closing alerts, as well as managing alert notes, logs, and custom properties through natural language.
168
MIT
jira-alerts-mcp
by rrvrs
Related Servers
Alternatives to jira-alerts-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables PagerDuty incident response operations including listing incidents, acknowledging and resolving incidents, looking up on-call schedules, and listing services.MIT
- AlicenseAqualityCmaintenanceEnables issue search, creation, updates, comments, status transitions, and project listing in Jira, purpose-built for security incident management and SOC workflows.9118Apache 2.0
- FlicenseNot gradedqualityCmaintenanceMCP server for Opsgenie (Atlassian's incident/alert management and on-call platform) exposing the full public Opsgenie REST API as MCP tools.-
- AlicenseAqualityAmaintenanceEnables interaction with Atlassian Jira and Confluence via their REST API, providing tools for searching, creating, updating, commenting, and retrieving issues, pages, projects, and spaces.14603MIT
- FlicenseAqualityFmaintenanceEnables interaction with Jira and Confluence APIs to search, create, and manage issues, pages, comments, and attachments across both Atlassian platforms.7-
TDQS
A4.4/5.0
Scored across 28 tools
Disambiguation5/5
Every tool maps to a distinct resource and action, and the descriptions actively call out neighboring tools to prevent confusion (e.g. logs vs notes, create vs add note, close vs delete, current vs next on-call). There is no pair of tools that appears to do the same thing.
Naming Consistency4/5
All tools share the jsm_ prefix and follow a snake_case verb_noun pattern, with consistent list/get/update/delete pairs throughout. Minor deviations exist between create_alert vs add_alert_* for creating versus attaching, and delete vs remove for notes versus tags/properties, but the conventions are still predictable.
Tool Count3/5
28 tools is on the high side, though the server covers two related domains—alert lifecycle and on-call schedules—plus async verification and capability discovery. The granularity is justified by distinct operations, but the surface is heavy for an agent to scan at a glance.
Completeness4/5
The alert lifecycle is thoroughly covered: create, read, list, update, acknowledge, snooze, close, delete, assign, escalate, responders, notes, tags, extra properties, and logs. Notable gaps are the lack of a remove-responder tool and no way to list escalation policies, teams, or custom action names, which sometimes forces the user to supply ids manually.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive