# Notification Center connectors

Manage [Notification Center connectors](https://coralogix.com/docs/user-guides/notification-center/connectors/index.md) directly from your AI agent. The Model Context Protocol (MCP) server provides a unified tool to create, retrieve, update, and delete connectors, and to generate infrastructure-as-code definitions from connector configurations.

## Tool

Use `manage_connectors` for all connector operations.

| Action value          | Description                                                                                                                                                                                           |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `create`              | Create a new connector.                                                                                                                                                                               |
| `get`                 | Retrieve a specific connector by ID.                                                                                                                                                                  |
| `list`                | List connectors with an optional case-insensitive name filter.                                                                                                                                        |
| `update`              | Update an existing connector. The agent retrieves the current configuration first, then applies your changes.                                                                                         |
| `delete`              | Delete a connector 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](https://coralogix.com/docs/developer-portal/infrastructure-as-code/coralogix-operator/index.md).                            |
| `generate_terraform`  | Generate Terraform configuration for the [Coralogix Terraform Provider](https://coralogix.com/docs/developer-portal/infrastructure-as-code/terraform-provider/coralogix-terraform-provider/index.md). |

## Example prompts

### Create a generic connector

```text
Create a Coralogix generic HTTPS Notification Center connector named
generic-alerts-connector. Use URL https://webhook.example.com/alerts,
method POST, and header Content-Type=application/json.
```

### Create a Slack notification connector

```text
Create a Coralogix Slack connector named slack-alerts-connector.
Use integrationId prod-slack-integration, fallbackChannel alerts,
and channel alerts.
```

### Export connector configuration

```text
Generate OpenAPI JSON, Kubernetes YAML, and Terraform configuration for the connector
named generic-alerts-connector.
```

## Important behaviors

- **Update requires retrieval first.** Retrieve the current connector, modify it, then update with the complete connector definition.
- **Use supported connector types.** Use connector types supported by the shared infrastructure-as-code subset.
- **Some override entity types are output-specific.** A connector that Terraform can represent might still fail for Kubernetes YAML if the operator does not support the requested override shape.