# MCPJungle

A self-hosted MCP gateway that lets teams register many MCP servers once and expose them behind a single endpoint with centralized discovery and access control.

MCPJungle is a self-hosted MCP gateway for developers and teams who run multiple Model Context Protocol servers and want to avoid scattered per-client configuration, duplicated setup, and inconsistent access control. Instead of wiring every MCP server into every AI client separately, servers are registered once in MCPJungle, and clients such as Claude, Cursor, or Codex connect to a single MCP endpoint.

It can be run locally to keep a personal MCP setup organized, or run as shared infrastructure for a team, with centralized discovery of tools, prompts and resources, optional tool groups that expose only the tools a given client should see, and basic access-control and observability hooks.

It starts locally with Docker Compose, which exposes a streamable HTTP MCP server; a CLI is used to register additional MCP servers with the gateway.

Website: https://docs.mcpjungle.com