Update an OpsGenie notification integration by providing the notification ID, name, API key, and event severities to include.
MIT
306,442 tools. Last updated 2026-07-26 23:57
"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
- Remove a service from the Datadog Opsgenie integration to manage monitoring and alert configurations.Apache 2.0
- Set up alert delivery by creating notification channels that route alerts to email, Slack, PagerDuty, webhooks, and 20+ other services.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
- Create a new service object in the Opsgenie integration to enable alert routing and incident management through Datadog.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 a new Axiom notifier using a JSON payload. The payload must include name and properties; configure one notification channel such as email, slack, webhook, customWebhook, pagerduty, opsgenie, discord, discordWebhook, or microsoftTeams. For custom webhooks, use properties.customWebhook with required url and body, plus optional headers and secretHeaders; body supports Go-template variables such as .Action, .MonitorID, .Body, .Title, and .Value.Connector
- List recent production incidents from PagerDuty or OpsGenie with their severity, MTTR (mean time to recovery), and affected services. Use this to understand reliability posture or investigate a recent outage in context with deployment activity. Read-only.Connector