# MCP Lifecycle Operator (/docs/ai/components/mcp-lifecycle-operator)



## Component Category [#component-category]

AI tools / MCP Server lifecycle

## Component Description [#component-description]

MCP Lifecycle Operator reconciles managed Model Context Protocol server workloads from declarative Kubernetes resources. It creates and updates the server deployment, service, and reported runtime status used by the BSQAI API and portal.

## Why It Is Used [#why-it-is-used]

In BullSequana AI, MCP Lifecycle Operator gives managed MCP Servers a dedicated controller and lifecycle API. This separates workload reconciliation from the BSQAI API while keeping server creation, updates, health, and deletion observable.

## Learn More [#learn-more]

* [MCP Lifecycle Operator project](https://github.com/kubernetes-sigs/mcp-lifecycle-operator)
* [MCP Lifecycle Operator releases](https://github.com/kubernetes-sigs/mcp-lifecycle-operator/releases)

## Deployment notes [#deployment-notes]

The operator runs in `mcp-lifecycle-operator-system`. Managed MCP Server workloads run in the isolated `mcp-servers` namespace behind a default NetworkPolicy. The platform mirrors the operator image into its private registry and installs the upstream CRD and controller with the required image-pull configuration.

Remote MCP Servers do not create operator-managed workloads. The BSQAI API stores their HTTPS address and reaches them through the MCP Gateway.

## Interacts With [#interacts-with]

* `BSQAI API`, which creates managed server resources and reports their status.
* `MCP Gateway`, which authenticates callers and injects linked upstream credentials.
* `AI Web Portal`, which manages server definitions, credentials, and tool allowlists.
* `Keycloak`, which authenticates users and identifies the active tenant.