camunda · Copilot · Mar 31, 2026 · Mar 31, 2026
diff --git a/...s-tools/orchestration-cluster-api-mcp/orchestration-cluster-api-mcp-overview.md b/...s-tools/orchestration-cluster-api-mcp/orchestration-cluster-api-mcp-overview.md
@@ -52,7 +52,7 @@ The MCP server uses the [Streamable HTTP](https://modelcontextprotocol.io/specif
 The MCP server is available from Camunda 8.9 onwards.
 :::
 
-If you have a local Orchestration Cluster running with [Camunda 8 Run](/self-managed/quickstart/developer-quickstart/c8run.md), the MCP server is enabled by default. Connect any MCP client using this configuration:
+If you have a local Orchestration Cluster running with [Camunda 8 Run](/self-managed/quickstart/developer-quickstart/c8run.md) or [Docker Compose](/self-managed/quickstart/developer-quickstart/docker-compose.md), the MCP server is enabled by default. Connect any MCP client using this configuration:
 
 ```json
 {

diff --git a/...apis-tools/orchestration-cluster-api-mcp/orchestration-cluster-api-mcp-setup.md b/...apis-tools/orchestration-cluster-api-mcp/orchestration-cluster-api-mcp-setup.md
@@ -12,7 +12,7 @@ Enable the Orchestration Cluster MCP Server and configure MCP clients to connect
 
 ## Enable the Orchestration Cluster MCP Server
 
-The MCP server is opt-in and must be enabled before MCP clients can connect.
+The MCP server is enabled by default in Camunda 8 Run and Docker Compose. For other deployment types, it must be explicitly enabled before MCP clients can connect.
 Depending on your deployment, enable it as follows:
 
 <Tabs groupId="deployment" defaultValue="c8run" queryString values={[
@@ -30,14 +30,7 @@ The MCP server is **enabled by default** in Camunda 8 Run. No additional configu
 
 <TabItem value="docker-compose">
 
-Set the `CAMUNDA_MCP_ENABLED` environment variable on the Orchestration Cluster container:
-
-```yaml
-services:
-  camunda:
-    environment:
-      CAMUNDA_MCP_ENABLED: "true"
-```
+The MCP server is **enabled by default** in the Docker Compose distribution. No additional configuration is needed.
 
 </TabItem>
 

diff --git a/docs/reference/announcements-release-notes/890/890-release-notes.md b/docs/reference/announcements-release-notes/890/890-release-notes.md
@@ -50,7 +50,7 @@ The Orchestration Cluster now exposes its operational capabilities via a built-i
 - Connect any MCP-compliant client (such as VS Code, GitHub Copilot, or Claude Code) to discover and invoke Camunda tools without custom API integration code.
 - Available tools cover process definitions, process instances, user tasks, incidents, and variables.
 - Streamable HTTP transport is supported, using the same authentication model as the REST API.
-- The MCP server is enabled by default in Camunda 8 Run. You can enable the MCP server in Camunda SaaS via your cluster settings in Console.
+- The MCP server is enabled by default in Camunda 8 Run and Docker Compose. You can enable the MCP server in Camunda SaaS via your cluster settings in Console.
 
 <p class="link-arrow">[Orchestration Cluster MCP Server](/apis-tools/orchestration-cluster-api-mcp/orchestration-cluster-api-mcp-overview.md)</p>
-Original file line number
+Diff line change
@@ Expand Up @@
     The MCP server is available from Camunda 8.9 onwards.
     :::
-    If you have a local Orchestration Cluster running with [Camunda 8 Run](/self-managed/quickstart/developer-quickstart/c8run.md), the MCP server is enabled by default. Connect any MCP client using this configuration:
+    If you have a local Orchestration Cluster running with [Camunda 8 Run](/self-managed/quickstart/developer-quickstart/c8run.md) or [Docker Compose](/self-managed/quickstart/developer-quickstart/docker-compose.md), the MCP server is enabled by default. Connect any MCP client using this configuration:
     ```json
     {
@@ Expand Down @@