Hosting

self-hosted

Transport

Streamable HTTP

Endpoint

Local process; no hosted endpoint documented

Authentication

Development mode has no client access control; enterprise mode supports authenticated clients and explicit server permissions.

Requirements

• Docker and Docker Compose for the documented local gateway setup.
• The MCPJungle CLI to register and manage upstream MCP servers.
• An MCP client that supports Streamable HTTP; Codex CLI supports URL-based remote servers.
• If registering stdio upstream servers in Docker, use the documented stdio-enabled image, which includes npx/uvx support.

Setup steps

1. Download the official `docker-compose.yaml` from https://raw.githubusercontent.com/mcpjungle/MCPJungle/refs/heads/main/docker-compose.yaml, then run `docker compose up -d`. The documented local endpoint is `http://localhost:8080/mcp`.
2. Install the MCPJungle CLI from the official releases page (Homebrew is documented for macOS). Register an upstream Streamable HTTP MCP with `mcpjungle register --name <server_name> --url <upstream_mcp_url>`, replacing those values with the name and endpoint of the server you intend to connect.
3. For an upstream stdio server, create a JSON config using the documented `name`, `transport: stdio`, `command`, `args`, and optional `env` fields, then run `mcpjungle register -c <config_file>`.
4. Add the local gateway to Codex with `codex mcp add mcpjungle --url http://localhost:8080/mcp`, then run `codex mcp list` and inspect the gateway's tools after both services are running.
5. Use `mcpjungle list tools` to see the registered tools. Names are qualified as `<server_name>__<tool_name>`. Use tool groups or enterprise-mode client permissions to expose only the tools needed by a client.
6. For team use, follow the official access-control guide and enable enterprise mode before exposing the endpoint. Do not expose a local development-mode endpoint to an untrusted network.

No individual tool names are documented in the reviewed sources.

Gateway forwards tools, prompts and resources from the upstream servers registered in that installation; tool names are namespaced as <server-name>__<tool-name>.

• Connection, tools/list, and a representative tool call were not independently tested for this catalog record.
• The local development mode has no access control; clients can reach every registered upstream server. Use enterprise mode and client restrictions for team deployments.
• The gateway does not supply tools on its own; users must register upstream MCP servers first.
• Upstream OAuth support is beta, limited to Streamable HTTP upstreams, and stores a token shared across the gateway; per-user OAuth is unsupported.
• Upstream tools may read, modify, or delete data according to their own capabilities and permissions. Review and limit access before registering them.
• The Dashboard UI is described by official documentation as being in beta.

• official product documentation

  Describes self-hosted local/team use, centralized discovery, tool groups, enterprise client access control, and the Dashboard UI beta.

• official repository

  Official MCPJungle repository describes the gateway, upstream server registration, dynamic tool discovery, qualified tool names, and its security model.

• official access control documentation

  Official governance overview documents enterprise-mode client tokens and per-server access policies; development mode grants clients full access to registered servers.

• official upstream authentication documentation

  Documents upstream bearer credentials and beta OAuth for Streamable HTTP upstreams; OAuth tokens are gateway-wide and per-user OAuth is unsupported.

• official codex mcp client documentation

  Documents the Codex CLI command format `codex mcp add <name> --url <url>` and shared MCP configuration for Codex CLI and IDE extension.

• verified repository owner avatar

  MCPJungle GitHub organization avatar downloaded, decoded as a PNG, and visually reviewed on light and dark contact sheets. Repository README had no standalone product logo; selected fallback tier D: verified project-owner avatar.

• discovery directory

  The October 17 research shortlist included MCPJungle as an MCP gateway candidate; the directory was used for discovery only, not proof of setup or current operation.

• official publisher documentation

  Official docs describe a self-hosted aggregator whose exposed tools are the registered upstream servers and selected groups.

• official crawl4ai tool inventory audit

  Crawl4AI 0.9.5 fetched the selected documentation page. No exact MCP tool identifiers were present in the captured page content; where attempted, the hosted tools/list endpoint required authorization.

• official crawl4ai tool inventory audit

  Gateway tool inventory is sourced from configured upstream servers and deployment/group configuration; no static universal list is published.

Documentation checked 2026-10-28T20:30:00.000Z. Connection has not been runtime tested.