MCPJungle and mcp-gateway
These are competitors offering alternative self-hosted MCP gateway solutions, with MCPJungle providing a general-purpose gateway framework while mcp-gateway adds enterprise security features (OAuth, DCR, analytics, firewall) on top of similar core routing functionality.
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
hyprmcp/mcp-gateway
MCP OAuth Proxy incl. dynamic client registration (DCR), MCP prompt analytics and MCP firewall to build enterprise grade MCP servers.
Implements a reverse proxy architecture that intercepts MCP traffic over HTTP, handling OAuth2 authentication transparently before routing requests to upstream MCP servers—eliminating the need to embed auth logic directly in server code. Provides observability through prompt telemetry and request payload inspection, enabling debugging and usage analytics without server-side instrumentation. Built in Go, it supports streamable HTTP MCP servers and automatically manages OAuth client registration, reducing operational complexity for enterprise deployments.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work