MCPJungle

MCPJungle is a lightweight open-source MCP gateway that aggregates multiple upstream MCP servers under a single endpoint. The project targets simple bundling — exposing a curated set of MCP tools to clients like Claude Desktop, Cursor, or Continue — without the operational surface of larger MCP gateways.

What it does

Operators list upstream MCP servers in a YAML config file, each identified by a transport (stdio, SSE, or streamable-HTTP) and connection details. The gateway aggregates tool listings from all upstreams and exposes them behind a single client-facing endpoint. Client authentication uses API keys defined in the same config.

Configuration updates are reloaded without restart. Tool discovery and listing behave consistently across all three transports.

Licensing

Mozilla Public License 2.0 (MPL-2.0), a weak per-file copyleft. Modifications to MCPJungle's own source files must be shared under MPL; incorporating MCPJungle unmodified into a larger application does not trigger copyleft on that application.

Deployment

Single Docker container. YAML configuration file for servers and API keys. No database required for basic deployments.

Limitations

• No generic OIDC integration — authentication is API-key only. Admin SSO against providers like Zitadel or Keycloak requires fronting the admin surface with a reverse-proxy auth middleware.
• ACLs are coarse — per-key access to a server is supported, but per-tool or per-client fine-grained filtering is not built in.
• Audit is basic request logging without retention policy controls.
• Small maintainer base; release cadence and issue response times reflect a project earlier in its lifecycle than the larger MCP gateways.
• No LLM proxy features — MCP aggregation only.