MCPJungle and mcp-gateway
These are competitors offering alternative approaches to MCP gateway architecture—MCPJungle emphasizes self-hosted simplicity while mcp-gateway prioritizes plugin-based extensibility and enterprise orchestration—but developers typically select one based on whether they prioritize ease of deployment or customizable agent composition.
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
lasso-security/mcp-gateway
A plugin-based gateway that orchestrates other MCPs and allows developers to build upon it enterprise-grade agents.
Supports pluggable security guardrails (basic token masking, PII detection via Presidio, and advanced policy enforcement via Lasso) that intercept and sanitize MCP requests/responses before reaching LLMs. Exposes `get_metadata` and `run_tool` endpoints to provide unified discovery and execution across proxied MCPs, while optionally scanning server reputation via Lasso Security's API. Integrates with Cursor and Claude Desktop through standard `mcp.json` configuration, with Docker support for containerized deployment.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work