Docker MCP Gateway is Docker's open-source orchestration layer for Model Context Protocol servers. It gives MCP clients one gateway, launches catalog servers in isolated containers on demand, injects credentials, applies runtime restrictions, and routes tool requests. Catalogs and profiles let teams reuse approved server collections across clients, while Docker Desktop can run the gateway automatically with MCP Toolkit enabled.
Alternatives to ToolHive
2 editor-selected alternatives · ToolHive overview →
source: tools.alternatives · stored order · active records only; review scores are annotations and never change membership or order
A directional evidence panel appears only when the substitute rationale, trade-offs, sources, and verification date have been recorded. Older selections without that panel remain visible but are unclassified under the new evidence contract.
mcp-proxy is a protocol bridge that converts MCP servers using stdio transport into HTTP and Server-Sent Events endpoints accessible over the network. This enables remote MCP server hosting, load balancing, and sharing servers across multiple AI clients. Supports both directions: wrapping stdio servers with HTTP and connecting to remote SSE servers through local stdio. Over 2,400 GitHub stars.
Open-source ToolHive alternatives
Docker MCP Gateway, mcp-proxy — see all open-source developer tools.
Free ToolHive alternatives
Docker MCP Gateway offer a free plan or free tier.
More MCP Servers tools
same category, not editor-selected alternatives — see how ToolHive compares →
FAQ
Which ToolHive alternative is listed first?
Docker MCP Gateway is first in the editor-selected list of 2 ToolHive alternatives and carries an editorial review score of 87/100. The stored order is editorial; review scores do not determine membership or position.
Are there open-source ToolHive alternatives?
Yes — Docker MCP Gateway, mcp-proxy are open source.
Are there free ToolHive alternatives?
Yes — Docker MCP Gateway offer a free plan or free tier.