Update an OpsGenie notification integration by providing the notification ID, name, API key, and event severities to include.
MIT
521,912 tools. Updated 2026-09-06 12:28
"Opsgenie" matching MCP tools:
- Create an OpsGenie notification integration to send monitoring alerts from Bluematador to OpsGenie, filtering by specified severities like alert, warning, and anomaly.MIT
- Retrieve open OpsGenie alerts with ID, message, priority, and status for monitoring incident response.MIT
- Acknowledge open OpsGenie alerts to prevent escalations and manage incident response workflows within observability platforms.MIT
- Acknowledge an OpsGenie alert with a dry-run safety check to avoid unintended actions.Apache 2.0
- Close an OpsGenie alert by ID, with optional note and reason. Use dry_run to verify the action without sending.Apache 2.0
Matching MCP Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for Opsgenie (Atlassian's incident/alert management and on-call platform) exposing the full public Opsgenie REST API as MCP tools.-
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive Opsgenie alert management including listing, creating, acknowledging, and closing alerts, as well as managing alert notes, logs, and custom properties through natural language.168MIT
- Create a new service object in the Opsgenie integration to enable alert routing and incident management through Datadog.Apache 2.0
- Remove a service from the Datadog Opsgenie integration to manage monitoring and alert configurations.Apache 2.0
- Retrieve a specific service configuration from the Datadog Opsgenie integration to manage alert routing and incident response workflows.Apache 2.0
- Retrieve all services configured in the Datadog Opsgenie integration for monitoring and alert management purposes.Apache 2.0
- Modify a service configuration in the Datadog Opsgenie integration to maintain accurate alert routing and incident management.Apache 2.0
- Create an alert channel to send incident notifications to email, Slack, webhook, or other services. Configure name, type, and provider details to start receiving alerts.MIT
- Bind external systems (ticketing, alerts, Slack, monitors) to FleetQ so events become signals that trigger rules and agents. Query and extend the knowledge graph for agent reasoning.AGPL 3.0
- List all third-party integrations configured in LogicMonitor, including Slack, PagerDuty, ServiceNow, and Jira, with status and configuration details.AGPL 3.0
- Set up or update an integration for a project, supporting Prometheus, ClickHouse, AWS, Slack, Teams, PagerDuty, Opsgenie, and webhooks.MIT
- Identify current on-call personnel across all schedules to determine who to contact for incidents.MIT
- List all configured integrations for a Coroot project, showing status for Prometheus, ClickHouse, AWS, Slack, Teams, PagerDuty, Opsgenie, and webhooks.MIT
- Create and configure new services with attributes like name, description, and associated IDs for integrations such as PagerDuty, Opsgenie, and GitHub.Apache 2.0
- All notification integrations in the project (Slack, Telegram, Discord, PagerDuty, OpsGenie, Teams, webhook, etc.).ConnectorNo auth