MCPJungle — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow routing, discovery, and deployment behavior as server fleets change

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Consolidating multiple MCP servers behind one governed endpoint.

What we know

Self-hosted MCP gateway for server registration, unified discovery, access control and observability.

Maintenance / activity evidence

Observed Aug 2, 2026 (UTC)feat(server): add --host / MCPJUNGLE HOST to choose the bind interfac…

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Gateway authority inherits downstream server capabilities. Writes: Register/deregister servers; Configure clients; Downstream writes.
Optional bearer token.
Sensitive access: Downstream MCP credentials/data

A gateway centralizes credentials and authority for many downstream MCP servers.

Security source · repository notice ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

1,291 repository stars

Stars observed Oct 6, 2026.

No canonical package metric applied.

All limitations / Review context

Does MCPJungle still provide the documented single-endpoint aggregation model?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

A gateway centralizes credentials and authority for many downstream MCP servers.
Gateway authority inherits downstream server capabilities.
Optional bearer token.
Tool traffic and configuration transit the gateway.
Reviewed write actions: Register/deregister servers; Configure clients; Downstream writes
Sensitive access: Downstream MCP credentials/data
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
Enterprise pricing
Persistence details
OAuth flow is not supported yet.
Enterprise-only features exist.

Original activity observations

2026-08-02T15:07:00Z: feat(server): add --host / MCPJUNGLE HOST to choose the bind interfac…

Technical identity

github.com/mcpjungle/mcpjungle

Exact implementation source: https://github.com/mcpjungle/mcpjungle ↗
Reviewed resource type: Gateway
Repository identity: mcpjungle/MCPJungle
Service endpoint: http://localhost:8080/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
mcpjungle/mcpjungle
Recorded repository material and project history.
Includes references whose attribution is not established.

Setup · Watchlist

Self-hosted gateway service setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Gateway provides access to all registered upstream tools; configure authorization and avoid public unauthenticated exposure.
Documentation-only: user must review side effects, account credentials, version and platform before running.
Download and inspect compose file, ports, volumes and permissions before deployment. Review environment effects, installation permissions, and publisher scripts before running. Source-backed ordered steps assembled from publisher README; not claimed to be one verbatim block.
Purpose detail: gateway_upstream_registration
Publisher JSON configuration for JSON-based MCP clients; not Codex config.toml. Publisher-supported parameters assembled into a machine-readable JSON example; placeholders are user-specific and no real credentials are included. Treat as reviewed composed example rather than a verbatim executable test.
not provisioning or database deletion.
Preserve volumes/config unless explicitly backed up and deleted.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.

Install / connect
Publisher instructions
**Gateway, not one upstream MCP.** Publisher Docker route: download its `docker-compose.yaml` from the official repository and run `docker compose up -d` from that directory; configure MCPJungle endpoint/registry and separately register the selected upstream MCP servers.
publisher documented example · Publisher instructions · Review before use
```
docker compose up -d
```
package install · Publisher instructions · Review before use
```
curl -O https://raw.githubusercontent.com/mcpjungle/MCPJungle/refs/heads/main/docker-compose.yaml
docker compose up -d
```
client registration · Publisher instructions
mcpjungle register --name context7 --url https://mcp.context7.com/mcp
Configure / authenticate
MCP100 setup guide
MCPJungle is self-hosted MCP gateway. Start via docker compose up -d per README, then register gateway endpoint/transport for client. Default Docker image lacks npx/uvx runtimes; stdio image is separate.
Advanced configuration · claude desktop json · MCP100 composed guide
claude desktop json · MCP100 composed guide
{ "mcpServers": { "mcpjungle": { "args": [ "mcp-remote", "http://localhost:8080/mcp", "--allow-http" ], "command": "npx" } } }
Check connection
Suggested check
Confirm `docker compose ps` for the deployment and check MCPJungle registry server health/client tool discovery. Upstream tools need separate verification.
Remove / uninstall / revoke
MCP100 setup guide
In MCPJungle deployment directory, stop its compose stack; unregister gateway MCP connection separately. Never add `-v` without explicit desire to delete volumes.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
docker compose down

Official Documentation & Sources

What it does

Self-hosted MCP gateway for server registration, unified discovery, access control and observability.

Capability: Developer Tools
Resource type: Gateway
Best fit: Consolidating multiple MCP servers behind one governed endpoint.

Representative uses

Run a local/shared gateway
Register remote MCP servers
Expose one /mcp endpoint
Forward bearer credentials

Limitations

OAuth flow is not supported yet.
Enterprise-only features exist.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Optional bearer token.
Permissions: Gateway authority inherits downstream server capabilities.
Data handling: Tool traffic and configuration transit the gateway.
Cost: free
Risk and cautions: A gateway centralizes credentials and authority for many downstream MCP servers.

Access scope and cautions

Write actions: Register/deregister servers Configure clients Downstream writes
Sensitive access: Downstream MCP credentials/data
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Run a local/shared gateway; Register remote MCP servers; Expose one /mcp endpoint; Forward bearer credentials.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded endpoint: http://localhost:8080/mcp. Recorded transport: streamable_http. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Optional bearer-token flag; OAuth not supported yet.

Can it modify data or perform write operations?

Documented write actions include: Register/deregister servers; Configure clients; Downstream writes. Recorded permission boundary: Gateway authority inherits downstream server capabilities.

What data-handling boundary should I consider?

Tool traffic and configuration transit the gateway. Recorded sensitive-access context: Downstream MCP credentials/data.

What limitations and risks should I check before use?

A gateway centralizes credentials and authority for many downstream MCP servers. OAuth flow is not supported yet. Enterprise-only features exist. A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.

Is this an official MCP?

MCPJungle is listed as First-party MCP in MCP100’s current evidence.