MCPJungle
MCPJungle is a self-hosted gateway for MCP servers. Developers register servers and their tools in one place using a CLI, and MCP clients connect to the single gateway endpoint to discover and call everything. The README names three audiences: developers using clients such as Claude and Cursor, developers building production agents that need access control, and organisations wanting to see all client and server interactions centrally in their own datacenter.
Quick start is `docker compose up -d` using the project's compose file, then installing the `mcpjungle` CLI with Homebrew or from the releases page, and registering a server such as context7. It supports Streamable HTTP servers and stdio servers (for `npx` or `uvx` based ones, use the larger `stdio`-tagged image). Other features covered are global enable or disable of tools, prompts, tool groups, authentication, and enterprise-mode features: access control and OpenTelemetry metrics at a `/metrics` endpoint. The database defaults to SQLite and PostgreSQL is supported for serious deployments.
The README lists limits plainly. SSE support exists but is described as not mature, and OAuth for upstream MCP servers is not supported yet. The licence is not stated in the README text we have, so check the repository before depending on it. Last push was 2026-08-02. This review is based on the README and repository data; we have not run it ourselves.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-25
- Commits, last 90 days
- 2
- Releases, last 90 days
- 1
- Latest release
- 0.4.6 (2026-08-02)
- Open issues
- 113
- Recent issues with at least one comment
- 14/28
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #20 Support stdio MCP servers47 comments · 2025-07-23
- #99 Unable to create password for groups in production mode20 comments · 2025-09-12
- #254 Support per-user upstream authentication through mcpjungle11 comments · 2026-05-07
- #279 Support http_proxy, https_proxy and no_proxy variables5 comments · 2026-06-16
- #103 Allow a client to search for Tools5 comments · 2025-09-13
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You want one gateway endpoint for many MCP servers, managed from a CLI.
- You want tool groups, global enable or disable of tools, and prompts.
- You want to start with docker compose, using SQLite by default and PostgreSQL for larger deployments.
- You need OAuth to upstream MCP servers: the README says it is not supported yet, and SSE support is described as immature.
- You need clear licence terms: the README text shows no licence, so check the repository.
- You want access control and OpenTelemetry metrics in the open build: the README attaches them to enterprise mode.
How it differs
vs mcphub★ 2.6kMCPJungle is CLI-first with registered servers and groups. MCPHub offers a web dashboard, OAuth 2.0 and smart routing under Apache-2.0.
Compatibility
Quick start
Use cases
Alternatives
Featured in these lists
Comments
No comments yet. Be the first!