Question: How to connect the STDIO backend from a container?

[qdrddr]

In Docker Compose, I see standalone optional container drop-in helpers such as MCP-fetch and MCP-time that expose STDIO protocols. How can I connect those to context-forge via STDIO?

mcp-context-forge/docker-compose.yml

Lines 279 to 311 in f7d8895

	# OPTIONAL MCP SERVERS – drop-in helpers the Gateway can call
	# ###############################################################################
	# mcp_time:
	# image: mcp/time:latest
	# networks: [mcpnet]
	# mcp_playwright:
	# image: mcp/playwright:latest
	# networks: [mcpnet]
	# mcp_postgres:
	# image: mcp/postgres:latest
	# networks: [mcpnet]
	# mcp_github:
	# image: mcp/github:latest
	# networks: [mcpnet]
	# mcp_filesystem:
	# image: mcp/filesystem:latest
	# networks: [mcpnet]
	# mcp_perplexity_ask:
	# image: mcp/perplexity-ask:latest
	# networks: [mcpnet]
	# mcp_memory:
	# image: mcp/memory:latest
	# networks: [mcpnet]
	# mcp_fetch:
	# image: mcp/fetch:latest
	# networks: [mcpnet]

Relates to #114

[crivetimihai]

Hi, the MCP server itself needs to support SSE, or using a similar supergateway or mcpgateway.translate layer to convert this to SSE before adding it to the catalog. A sidecar can also work here.

But right now, this won't work 'as-is' if the container itself doesn't support SSE, without the use of supergateway, mcpgateway.translate or a sidecar.