MCPJungle

MCPJungle is a self-hosted MCP gateway for developers and teams who want to manage multiple MCP servers without scattered client configurations, duplicated setup, or inconsistent access control. Servers are registered once, and clients such as Claude, Cursor, Codex, GitHub Copilot, or custom agents connect to a single streamable HTTP endpoint at /mcp. It is open source under the MPL-2.0 license and written in Go.

What It Is

MCPJungle sits between AI clients and upstream MCP servers. It aggregates the tools, prompts, and resources of every registered server and presents them through one gateway. It can run locally in development mode for an individual, or in enterprise mode as shared infrastructure for a team.

How the Workflow Operates

The gateway starts via Docker Compose or the standalone binary, backed by SQLite or PostgreSQL. A CLI registers upstream servers over Streamable HTTP or STDIO (SSE is supported but deprecated), and can list, invoke, enable, and disable tools and prompts. Tools use canonical names of the form server__tool. Tool Groups expose curated subsets of tools on their own endpoints so each client sees only what it needs. Stateless connections are the default, and stateful sessions are available for servers with slow cold starts.

Access Control and Operations

In enterprise mode, MCP clients authenticate with bearer tokens and are explicitly allowed to reach specific servers, and user accounts exist for human operators. Upstream servers can be authenticated with static bearer tokens, custom headers, or a beta OAuth flow. Prometheus-compatible OpenTelemetry metrics are served at /metrics. The documentation lists the dashboard UI and resources support as beta, audit logs as limited, and OTLP export as not supported.