From cc03c99268547abb13f4cf3d69adafc95ca21b67 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Thu, 7 May 2026 09:25:59 +0000
Subject: [PATCH] [instructions] Update mcp-servers stdio example for MCP
 Gateway v0.1.5

MCP Gateway v0.1.5 requires stdio servers to use Docker-based configuration
(container + entrypoint). The previous example using command: "node" is now
rejected by the compiler. Update the syntax.md example to show both the
Docker-based stdio pattern and the HTTP transport pattern for runner-installed
servers.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .github/aw/syntax.md | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/.github/aw/syntax.md b/.github/aw/syntax.md
index 5e592b8ea80..096519e85bb 100644
--- a/.github/aw/syntax.md
+++ b/.github/aw/syntax.md
@@ -673,14 +673,23 @@ tools:
 
 ### Custom MCP Tools
 
+Stdio MCP servers must be Docker-based (use `container:` + `entrypoint:`). For Node/Python servers already installed on the runner, use HTTP transport instead:
+
 ```yaml
+# Stdio (Docker-based)
 mcp-servers:
   my-custom-tool:
-    command: "node"
-    args: ["path/to/mcp-server.js"]
+    container: "ghcr.io/my-org/my-tool:latest"
+    entrypoint: "my-tool"
     allowed:
       - custom_function_1
       - custom_function_2
+
+# HTTP (for Node/Python servers running on the runner)
+mcp-servers:
+  my-node-tool:
+    type: http
+    url: "http://localhost:8765/mcp"
 ```
 
 HTTP MCP servers are also supported with optional upstream authentication: