mcp-gateway-registry and MCPJungle
MCPJungle is a self-hosted gateway implementation, while mcp-gateway-registry is an enterprise registry layer that adds centralized discovery and OAuth management on top of gateway infrastructure—making them complementary tools that can be used together, with the registry providing governance for MCPJungle-like gateways.
About mcp-gateway-registry
agentic-community/mcp-gateway-registry
Enterprise-ready MCP Gateway & Registry that centralizes AI development tools with secure OAuth authentication, dynamic tool discovery, and unified access for both autonomous AI agents and AI coding assistants. Transform scattered MCP server chaos into governed, auditable tool access with Keycloak/Entra integration.
Implements a unified registry and gateway for both MCP servers and AI agents, enabling dynamic tool discovery and agent-to-agent communication through the A2A Protocol while maintaining centralized credential management and audit trails. Supports multi-protocol agent communication patterns with streamable HTTP transport for cloud-hosted infrastructure, integrating external registries like Anthropic's MCP Registry into a single control plane for governance across tools and agents.
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.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work