Mcpjungle Mcp Gateway

Name: Mcpjungle Mcp Gateway
Author: mcpjungle

@mcpjungle

Repository Homepage

About Mcpjungle Mcp Gateway

One place to manage & connect to all your MCP servers

#mcpjungle #mcp-gateway #ai-agents

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcpjungle-mcpjungle": {
      "command": "docker",
      "args": [
        "pull",
        "mcpjungle/mcpjungle"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Mcpjungle Mcp Gateway?

Mcpjungle Mcp Gateway (MCPJungle) is a self-hosted gateway that lets developers and teams run all their MCP (Model Context Protocol) servers behind a single endpoint. It consolidates scattered client configurations, reduces duplicated setup, and provides centralized access control and observability.

How to use Mcpjungle Mcp Gateway?

Start the gateway with Docker Compose (docker compose up -d) or run the binary directly (mcpjungle start). Use the CLI (mcpjungle register --name ... --url ...) to add MCP servers. Connect AI clients like Claude, Cursor, or Copilot by pointing them to the unified MCP endpoint at http://localhost:8080/mcp.

Key features of Mcpjungle Mcp Gateway

Single MCP endpoint for multiple AI clients
Centralized server registration and management
Unified discovery of tools, prompts, and resources
Optional tool groups to restrict client access
Access control and OpenTelemetry for shared deployments

Use cases of Mcpjungle Mcp Gateway

Local development: keep personal MCP setup clean and reproducible
Team infrastructure: share a central MCP gateway with discovery and access control
Multi‑client integration: connect Claude, Cursor, Copilot, and custom agents to one endpoint
Production deployments: deploy with Postgres and enterprise‑grade observability

FAQ from Mcpjungle Mcp Gateway

What is the difference between MCPJungle and a typical MCP server?

MCPJungle is a gateway that aggregates multiple MCP servers behind a single endpoint, offering centralized management, access control, and tool grouping—not just a single MCP server.

What dependencies or runtime does Mcpjungle Mcp Gateway require?

It runs as a standalone binary or Docker image. For development, it uses a SQLite database (default) or optional PostgreSQL. Docker images are available with or without stdio‑tool dependencies.

Where does my data live?

All registered server data and gateway state are stored in a configurable database (SQLite file or PostgreSQL). Deleting the database removes all configuration.

What transports does Mcpjungle Mcp Gateway support?

It supports Streamable HTTP (primary), stdio, and SSE (SSE support is not yet mature).

How does authentication work?

Authentication is an enterprise feature. In development mode, the gateway runs without authentication; production/enterprise mode enables access control and other enterprise features.