You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, MCP server images in the Docker MCP registry don’t indicate which transport(s) they expose/require (e.g., stdio, sse, streamableHTTP). Since some MCP clients need a specific transport to connect, this lack of information makes integration harder. Developers often have to experiment or read the source to figure out compatibility.
Add a field to the MCP registry metadata (or include in the Docker Hub listing) that specifies which transports the server supports.