From 9a032573f1eb68b12e316fc6b3ff4107ed2183ca Mon Sep 17 00:00:00 2001 From: "Paul B." Date: Mon, 18 May 2026 11:38:25 +0200 Subject: [PATCH] Use Config- prefixed header in example --- src/_help/mcp-servers/runtime-expressions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/_help/mcp-servers/runtime-expressions.md b/src/_help/mcp-servers/runtime-expressions.md index 1b26892b..f81745d2 100644 --- a/src/_help/mcp-servers/runtime-expressions.md +++ b/src/_help/mcp-servers/runtime-expressions.md @@ -132,10 +132,10 @@ Reference values tied to the user currently invoking the MCP server. Only availa ```yaml headers: Authorization: "Bearer $current_user.token" - X-Org-Id: "$current_user.org_id" + Config-Org-Id: "$current_user.org_id" ``` -For `$current_user.`, matching is case-insensitive, and underscores in the expression map to dashes in the header. All of `$current_user.api_key`, `$current_user.API_KEY` and `$current_user.Api-Key` resolve the same `Config-Api-Key` header. +For `$current_user.`, matching is case-insensitive, and underscores in the expression map to dashes in the header. All of `$current_user.org_id`, `$current_user.ORG_ID` and `$current_user.Org-Id` resolve the same `Config-Org-Id` header. If no matching header is sent by the client, the expression resolves to an empty string.