Notification Center presets
Manage Notification Center presets directly from your AI agent. The Model Context Protocol (MCP) server provides a unified tool to create, retrieve, update, and delete custom presets, and to generate infrastructure-as-code definitions from preset configurations.
Tool
Use manage_presets for all preset operations.
| Action value | Description |
|---|---|
create | Create a new custom preset. |
get | Retrieve a specific preset by ID. |
list | List presets with an optional case-insensitive name filter. |
update | Update an existing preset. The agent retrieves the current configuration first, then applies your changes. |
delete | Delete a preset by ID. |
generate_openapi | Generate the OpenAPI JSON payload for use with the Coralogix REST API. |
generate_kubernetes | Generate a Kubernetes Operator YAML manifest for the Coralogix Operator. |
generate_terraform | Generate Terraform configuration for the Coralogix Terraform Provider. |
Supported preset types
The tool supports Slack, generic HTTPS, PagerDuty, and email presets for alert notification use cases.
Example prompts
Create a Slack notification preset
Create a Slack Notification Center preset named slack-alert-summary.
Use parent preset preset_system_slack_alerts_basic and override title with
{{ alertDef.name }} and description with {{ alertDef.description }} for all alerts.
Create a subtype-specific preset
Create a Slack preset named slack-immediate-alerts. Use parent preset
preset_system_slack_alerts_basic and apply it only to subtype
logsImmediateTriggered. Override title with {{ alertDef.name }}.
Generate an email preset
Generate OpenAPI JSON, Kubernetes YAML, and Terraform configuration for an email preset
named email-alert-preview. Use parent preset preset_system_email_alerts,
entity type alerts, subtype logsImmediateTriggered, customSubject
{{ alertDef.name }}, and customContent <div>{{ alertDef.description }}</div>.
Do not create it.
Important behaviors
- The tool requires a parent preset ID. It rejects custom presets without a parent preset.
- Use supported connector types. For example, the tool does not support ServiceNow presets in this shared infrastructure-as-code subset.
- Preset conditions must use 1 condition shape. Do not mix entity-only and entity-plus-subtype match conditions in the same override.
- Update requires retrieval first. Retrieve the current preset, modify it, then update with the complete preset definition.
Theme
Light