MCPJungle

Self-hosted gateway and registry that exposes many MCP servers through one unified endpoint.

Open SourceSelf HostedOffline Capable
0.0 (0)

About

Instead of pasting the same server list into every client configuration, MCPJungle registers all of a team's MCP servers once and serves them to any agent through one unified endpoint. The MPL-2.0 licensed Go binary acts as both gateway and registry: clients connect over stdio or streamable HTTP, tool groups expose curated subsets of the catalog to different consumers, and stateful connections cut cold-start latency for servers that are expensive to spawn. An enterprise mode layers on access control and observability for organizations that need to govern which agents may call which tools. Deployment stays deliberately small: install a release binary, use the Homebrew tap, or run the ghcr.io Docker image, with Docker Compose recommended for local setups. Documentation lives at docs.mcpjungle.com. At about 1,200 GitHub stars the project is younger and leaner than heavyweight gateways like IBM's ContextForge, and that smaller footprint is precisely the appeal for individuals and small teams self-hosting a handful of servers rather than an enterprise fleet.

Should you use MCPJungle?

Pick it when

Pick MCPJungle when an individual or small team wants to register its MCP servers once and serve curated tool groups to every client from one self-hosted Go binary or Docker image.

Look elsewhere when

Skip it if you need REST or gRPC services translated into MCP tools or a large governed fleet, where ContextForge goes further, or if your worry is untrusted servers touching the host, which ToolHive's per-server containers address.

Alternatives to MCPJungle

  • IBM ContextForge

    Enterprise gateway with REST and gRPC translation, A2A federation, and OpenTelemetry export; far broader, but needs PostgreSQL and Redis.

  • ToolHive

    Isolates each server in its own container with secret management and a Kubernetes operator; stronger security posture, built around isolation rather than tool groups.

  • mcp-use

    Connects an agent to several servers from client code with nothing to host; fine for one app, but every client repeats its own server configuration.

Reviews (0)

Leave a Review

No reviews yet. Be the first to review!

Details

Price
Free
Platform
Local/Desktop
Difficulty
Easy (2/5)
License
MPL-2.0
Added
Aug 24, 2026

Tags