Notification Center routing
Manage Notification Center routing directly from your AI agent. The Model Context Protocol (MCP) server provides a unified tool to create, retrieve, update, and delete global routers, and to generate infrastructure-as-code definitions from router configurations.
Tool
Use manage_global_routers for all global router operations.
| Action value | Description |
|---|---|
create | Create a new global router. |
get | Retrieve a specific global router by ID. |
list | List global routers with an optional case-insensitive name filter. |
update | Update an existing router. The agent retrieves the current configuration first, then applies your changes. |
delete | Delete a global router 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. |
Example prompts
Create a router
Create a Coralogix global router named checkout-alert-routing.
Use routing labels environment=production, service=checkout, and team=platform.
Add fallback target connectorId <connector-id>. Add a rule named critical-alerts
for alerts where alertDef.priority == "P1" and route it to connectorId <connector-id>.
Preview a router
Generate OpenAPI JSON, Kubernetes YAML, and Terraform configuration for a global router
named checkout-routing-preview with fallback connectorId <connector-id> and
one alert rule named preview-rule with condition alertDef.priority == "P1".
Do not create it.
Export an existing router
Important behaviors
- Targets require connector IDs. Fallback and rule targets must include a connector ID.
- Rules need conditions. The tool rejects rules without conditions.
- Alert routing is the supported entity type. The tool rejects unsupported entity types.
- Update requires retrieval first. Retrieve the current router, modify it, then update with the complete router definition.
Theme
Light