# MCP notifications

> Tag 7: the client subscribes to the notifications of the container’s own MCP server; the server answers with one channel response per notification for the life of the connection, or an error at once.

Canonical: https://protocol.diverge.network/2.3.0/container-proxy-endpoints/tools-begin/client/mcp-notifications/
Specification revision: 2.3.0

The client opens this channel to hear what the container's MCP server
says on its own account. The server relays each notification as one
channel response from the moment the channel opens.

- **The request.** The tag byte `7` and nothing more.
  [Request](/2.3.0/container-proxy-endpoints/tools-begin/client/mcp-notifications/request/) states its form.
- **The response.** One channel response per notification, for as
  long as the connection lives, or exactly one error and the channel
  response finish. [Response](/2.3.0/container-proxy-endpoints/tools-begin/client/mcp-notifications/response/)
  states the sequence.
- **Many channels.** The client may open this channel more than
  once; each channel hears every notification from the moment it
  opened.