> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aient.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# integration.mcp.connected

> Webhook schema for ai.aient.integration.mcp.connected

# ai.aient.integration.mcp.connected

> Generated from `@aient/events`. Do not edit this page by hand.

An MCP client connection became usable.

## Delivery Contract

| Field            | Value                                                                         |
| ---------------- | ----------------------------------------------------------------------------- |
| Visibility       | Tenant-selectable public event                                                |
| Topic            | `v1.events.integrations`                                                      |
| Bounded context  | `integration`                                                                 |
| Source           | `https://aient.ai/api/organisations/{organisationId}`                         |
| Subject          | `integrations/mcp/{connectionKind}`                                           |
| Schema ID        | `sch_01KREWXD5AMEPBQ7TWS9TK5H8P`                                              |
| Immutable schema | `https://registry.aient.ai/schemas/sch_01KREWXD5AMEPBQ7TWS9TK5H8P.json`       |
| Version alias    | `https://registry.aient.ai/events/ai.aient.integration.mcp.connected/v1.json` |

## Payload Fields

| Field            | Required | Type     | Enum |
| ---------------- | -------- | -------- | ---- |
| `clientName`     | no       | `string` | -    |
| `connectionKind` | yes      | `string` | -    |
| `organisationId` | yes      | `string` | -    |
| `userId`         | no       | `string` | -    |

## Privacy Notes

ID-first customer-facing payload. Do not include secrets, tokens, raw telemetry, prompts, logs, or customer content.

## Lifecycle Notes

Emitted after the owning bounded-context state transition commits through its Restate handler.

## Compatibility Notes

Backward-compatible schema changes may add optional fields; removing fields, changing field types, or removing enum values requires a new schema revision and migration plan.

## Example CloudEvent

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "data": {
    "clientName": "Example name",
    "connectionKind": "example-connectionKind",
    "organisationId": "11111111-1111-4111-8111-111111111111",
    "userId": "user_example"
  },
  "datacontenttype": "application/json",
  "dataschema": "https://registry.aient.ai/schemas/sch_01KREWXD5AMEPBQ7TWS9TK5H8P.json",
  "id": "evt_01J8X7AKZP4N6QHF2T1Y3R5VAA",
  "organisationid": "11111111-1111-4111-8111-111111111111",
  "source": "https://aient.ai/api/organisations/11111111-1111-4111-8111-111111111111",
  "specversion": "1.0",
  "subject": "integrations/mcp/example-connectionKind",
  "time": "2026-04-25T12:00:00.000Z",
  "type": "ai.aient.integration.mcp.connected"
}
```