MCPJungle and mcp-gateway
These are competitors offering alternative approaches to MCP gateway infrastructure—MCPJungle emphasizes self-hosted deployment while mcp-gateway focuses on centralized registry and REST-to-MCP translation, requiring teams to choose one architectural pattern for their MCP server management.
About MCPJungle
mcpjungle/MCPJungle
Self-hosted MCP Gateway for AI agents
Provides a unified gateway that registers and brokers multiple MCP servers (both HTTP-based and stdio-based) through a single standardized endpoint, eliminating the need for AI agents to connect to each server individually. Integrates with Claude, Cursor, and Copilot via streamable HTTP transport at `/mcp`, with enterprise features including access control, OpenTelemetry observability, and stateful connection management for cold-start optimization.
About mcp-gateway
theognis1002/mcp-gateway
Model Context Protocol (MCP) Gateway & Registry - Central hub for managing tools, resources, and prompts for MCP-compatible LLMs. Translates REST APIs into MCP, builds virtual MCP servers with security and observability, and bridges multiple transports (stdio, SSE, streamable HTTP).
Built in Go with PostgreSQL and Redis backing, the gateway enforces fine-grained access control through JWT/OAuth2 authentication, RBAC policies, and content filtering—enabling secure multi-tenant namespaces where AI agents access isolated server groups. It implements automatic server discovery and health monitoring with failover capabilities, while supporting JSON-RPC 2.0, WebSocket, Server-Sent Events, and streamable HTTP transports to bridge diverse client needs with comprehensive audit logging and performance metrics.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work