[instructions] Sync mcp-servers stdio example with MCP Gateway v0.1.5#30801
Merged
pelikhan merged 1 commit intoMay 7, 2026
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Instructions Update — MCP Gateway v0.1.5 breaking change
This PR updates
.github/aw/syntax.mdto reflect a breaking change in MCP Gateway v0.1.5 that was already enforced in the compiler but not yet reflected in the documentation.Files Changed
syntax.md: Replace invalidcommand: "node"stdio example with correct Docker-based (container:+entrypoint:) and HTTP transport patterns.Background
MCP Gateway v0.1.5 dropped support for non-Docker stdio MCP servers. The compiler (
pkg/workflow/mcp_config_custom.go:71-80) now rejects any stdio server configured with a non-dockercommand (e.g.command: "node"). The previous example insyntax.mdwould fail compilation with an error like:The updated example shows both valid patterns:
container:+entrypoint:) — for containerized toolstype: http+url:) — for Node/Python servers installed on the runnerChangesets Reviewed
minor-update-mcpg-v0-1-5.md— MCP Gateway v0.1.5 breaking rules (Docker-only stdio, no mounts on HTTP)minor-rename-app-to-github-app.md— already documented ✓minor-rename-safe-inputs-to-mcp-scripts.md— already documented ✓minor-decouple-status-comment.md— already documented ✓minor-disable-agent-sandbox-only.md— already documented ✓minor-enable-reaction-status-comment-by-default.md— already documented ✓minor-preserve-branch-name-in-safe-outputs.md— already documented ✓minor-mcp-gateway-otlp-headers-string-only.md— affectsmcp-gateway.opentelemetry.headers(undocumented advanced field, not in instruction files)minor-add-cli-proxy-feature-flag.md— already documented ✓Size Audit
syntax.mdValidation
syntax.md)pkg/workflow/mcp_config_custom.go:71-80