From 25e796fe5433216f0c7c51746b20369e3f48f6b3 Mon Sep 17 00:00:00 2001
From: Daniel Meppiel <51440732+danielmeppiel@users.noreply.github.com>
Date: Sun, 24 May 2026 08:08:31 +0200
Subject: [PATCH] docs: document Docker workspace variable substitution for
 registry MCP servers

Registry-resolved MCP servers that use Docker with {workspaceFolder}
placeholder variables now receive correct workspace path substitution
across all harnesses (Copilot, Codex, Cursor, Claude, Gemini,
Windsurf, OpenCode). Adds a note to the install-mcp-servers guide
documenting this behavior after the fix in #1461.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
 docs/src/content/docs/consumer/install-mcp-servers.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs/src/content/docs/consumer/install-mcp-servers.md b/docs/src/content/docs/consumer/install-mcp-servers.md
index 6839109d2..ce1fd4c0d 100644
--- a/docs/src/content/docs/consumer/install-mcp-servers.md
+++ b/docs/src/content/docs/consumer/install-mcp-servers.md
@@ -141,6 +141,16 @@ MCP defines two transport families. APM exposes both:
   and `file://` are rejected). Use `--header KEY=VALUE` (repeatable)
   for HTTP headers such as `Authorization`.
 
+### Docker-based registry servers and workspace variables
+
+Some registry-resolved MCP servers run inside Docker containers and
+declare `{workspaceFolder}` in their runtime arguments to mount your
+project into the container. APM substitutes the current project root
+for `{workspaceFolder}` when writing the runtime config, so Docker
+volume mounts like `-v {workspaceFolder}:/workspace` resolve correctly
+across all supported harnesses: Copilot CLI, Codex, Cursor, Claude,
+Gemini, Windsurf, and OpenCode. (#1461)
+
 `--transport` is inferred when omitted: a `--url` implies a remote
 transport, a post-`--` command implies `stdio`. The mutually-exclusive
 combinations (`--url` plus stdio command, `--header` without `--url`,