Clarify MCP Gateway only supports containerized stdio and HTTP servers #9295
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.
The MCP Gateway specification incorrectly implied support for direct command execution (
stdio+commandwithout containerization). This creates ambiguity about supported transport mechanisms.Changes
Specification Updates (W3C style)
commandandargsfields, madecontainerrequired for stdio servers with explicit note thatcommandfield is NOT supportedcontainerfield instead ofcommandfieldExample Configuration
Before:
{ "mcpServers": { "example": { "command": "node", "args": ["server.js"] } } }After:
{ "mcpServers": { "example": { "container": "ghcr.io/example/mcp-server:latest", "entrypointArgs": ["--verbose"] } } }The specification now uses RFC 2119 keywords (MUST, SHALL NOT) consistently to clarify that direct command execution is explicitly unsupported.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.