From d826c7ac137d3d754f844bf676c2d782047529c6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?David=20Barrag=C3=A1n=20Merino?= Date: Tue, 18 Aug 2026 12:40:40 +0200 Subject: [PATCH] :books: Remove architectural constraints related to MCP Server HA --- docs/technical-guide/configuration.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/docs/technical-guide/configuration.md b/docs/technical-guide/configuration.md index 618b945df6..1541f1d3b8 100644 --- a/docs/technical-guide/configuration.md +++ b/docs/technical-guide/configuration.md @@ -438,7 +438,7 @@ with this flag enabled, the Penpot configuration will disable as well the librar The mechanisms for installing Penpot in HA depend largely on how each infrastructure is managed. In this section, we mention the key factors to consider when replicating a Penpot installation: -The components that can be replicated are the `frontend`, the `backend`, and the `exporter`. +The components that can be replicated are the `frontend`, the `backend`, the `exporter` and the `mcp`. Replication management depends on the infrastructure, whether it's a load balancer or a Kubernetes deployment with HPA. In a high-availability (HA) scenario, managing the state outside of replicas is crucial. This affects the following components: @@ -447,12 +447,6 @@ In a high-availability (HA) scenario, managing the state outside of replicas is - Valkey: Penpot only needs one Valkey instance to function correctly. Due to the nature of the data it manages, replication isn't even essential. - User media storage: This should not be configured with local storage but rather with centralized storage, such as Kubernetes PVC or S3. - -__Since version 2.15.0__ - -Starting with version 2.15, we have introduced the MCP server. Due to architectural constraints, using the MCP server requires running only a single instance of Penpot. -If the MCP server is not installed, then Penpot can scale normally and multiple application instances may be deployed without restrictions. - ## Backend This section enumerates the backend only configuration variables.