Our take
Activerecent releases- Activity
- 56
- Community
- 41
- Issues
- 47
- Pull requests
- 43
+324 stars in the last 30 days
- Releases more often than 76% of the projects we track
MCPJungle is an actively released Go gateway with useful local and team-oriented controls, though recent code changes and issue handling have been sparse and most contributions come from one person.
Good fit if
- You want one endpoint for multiple MCP servers and clients.
- You need self-hosted tool selection or client-to-server access controls.
- You can run the Go-based service with Docker Compose or configure its database and deployment yourself.
Look elsewhere if
- You require OAuth for upstream MCP authentication, which the README says is not yet supported.
- You need prompts available through tool groups, which are currently unsupported.
- You need a project with broadly distributed contributions, since most of the code comes from one person.
All health signals
| Last commit | 2026-08-02 (2 months ago) |
|---|---|
| Commits, last 90 days | 1 |
| Releases, last 12 months | 22 (latest 0.4.6, 2026-08-02) |
| Contributors | 22 (top contributor: 84% of commits) |
| Issues closed, last 90 days | 1 |
| Pull requests merged, last 90 days | 1 |
| Project age | 17 months |
Checked on 2026-10-10 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
1,619Forks
202Change since Nov 10, 2026: +3 stars·-1 forks
Overview
MCPJungle brings multiple Model Context Protocol (MCP) servers behind one endpoint. Instead of configuring each server separately in every AI client, you register them once and connect clients such as Claude, Cursor, or custom agents to the gateway.
It is aimed at developers who want a reproducible local MCP setup and teams that need shared discovery and access controls. The project is written in Go and can run locally or as shared infrastructure.
Key Features
- Exposes registered MCP servers through a single Streamable HTTP endpoint.
- Registers servers using Streamable HTTP or stdio transports.
- Provides a CLI to register servers, inspect and invoke tools, and manage prompts.
- Creates tool groups that expose selected tools through separate endpoints.
- Supports bearer tokens and custom headers for upstream MCP servers.
- Offers enterprise mode with client authentication, server access controls, and OpenTelemetry metrics.
- Supports SQLite by default and PostgreSQL for deployments that need it.
Use Cases
- A developer can keep a personal collection of MCP servers in one place and connect multiple AI clients to it.
- A team can host a shared gateway and control which registered servers each MCP client can access.
- An agent developer can expose a curated tool group instead of presenting a client with every registered tool.
- An organization using token-protected remote MCP servers can configure credentials centrally at registration.
What you need
Detected in the repository
- Go 1.24.3 or newer (from go.mod)
- A Dockerfile, so it can run in a container; a Compose file sets up the related services
License in plain words
MPL-2.0weak copyleft
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license notice
- Share your changes: yes, changes to MPL-licensed files, when you distribute them
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Start the local service with Docker Compose:
curl -O https://raw.githubusercontent.com/mcpjungle/MCPJungle/refs/heads/main/docker-compose.yaml
docker compose up -d
The default MCP endpoint is http://localhost:8080/mcp. See the README and documentation for setup and client configuration details.
Alternatives
- metamcp: MetaMCP also combines MCP servers behind unified endpoints, with namespace-level controls rather than MCPJungle's registry and gateway focus.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| MCPJungle | Go | MPL-2.0 | 1.3k | Active |
| metamcp | TypeScript | MIT | 2.7k | Quiet |
Considerations
The project is marked active and has continued publishing releases, but the measured recent period includes only one commit, one merged pull request, and one closed issue. It has 22 contributors, yet contribution activity is highly concentrated in one person, which is a maintenance continuity risk. The README also identifies OAuth support as unfinished and tool groups do not currently support prompts. Running it requires Go 1.24.3 for a source-based setup, or Docker and Docker Compose; persistent deployments need a database, with PostgreSQL supported as an option.
Found this useful?
Share it with someone who would like MCPJungle.