🌳 MCPJungle 🌳

curl -O https://raw.githubusercontent.com/mcpjungle/MCPJungle/refs/heads/main/docker-compose.prod.yaml

docker compose -f docker-compose.prod.yaml up -d

> [!NOTE]

> The enterprise mode used to be called production mode.

> The mode has now been renamed for clarity. Everything else remains the same.

This will start the MCPJungle server along with a persistent Postgres database container.
You can quickly verify that the server is running:

If you plan on registering stdio-based MCP servers that rely on npx or uvx, use mcpjungle's stdio tagged docker image instead.

> [!NOTE]

> If you're using docker-compose.yaml, this is already the default image tag.

> You only need to specify the stdio image tag if you're using docker-compose.prod.yaml.

This image is significantly larger. But it is very convenient and recommended for running locally when you rely on stdio-based MCP servers.
For example, if you only want to register remote mcp servers like context7 and deepwiki, you can use the standard (minimal) image.
But if you also want to use stdio-based servers like filesystem, time, github, etc., you should use the stdio-tagged image instead.
> [!NOTE]

> If your stdio servers rely on tools other than npx or uvx, you will have to create a custom docker image that includes those dependencies along with the mcpjungle binary.
Production Deployment
The default MCPJungle Docker image is very lightweight - it only contains a minimal base image and the mcpjungle binary.
It is therefore suitable and recommended for production deployments.
For the database, we recommend you deploy a separate Postgres DB cluster and supply its endpoint to mcpjungle (see Database section below).
You can see the definitions of the standard Docker image and the stdio Docker image.
If you're running MCPJungle in your organisation, we recommend running the Server in the enterprise mode:

mcpjungle start --enterprise

mcpjungle invoke calculator__multiply --input '{"a": 100, "b": 50}'

> [!NOTE]

> A tool in MCPJungle must be referred to by its canonical name which follows the pattern <mcp-server-name>__<tool-name>.

> Server name and tool name are separated by a double underscore __.

>

> eg- If you register a MCP server github which provides a tool called git_commit, you can invoke it in MCPJungle using the name github__git_commit.

> 

> Your MCP client must also use this canonical name to call the tool via MCPJungle.
The config file format for registering a Streamable HTTP-based MCP server is:

You can disable and re-enable a specific tool or all the tools provided by an MCP Server.

If a tool is disabled, it is not available via the MCPJungle Proxy or any of the Tool Groups, so no MCP clients can view or call it.
You can disable and enable Prompts as well.

mcpjungle disable tool context7__get-library-docs

mcpjungle enable tool context7__get-library-docs

As you add more MCP servers to MCPJungle, the number of tools available through the Gateway can grow significantly.

If your MCP client is exposed to hundreds of tools through the gateway MCP, its performance may degrade.

MCPJungle allows you to expose only a subset of all available tools to your MCP clients using Tool Groups.

You can create a new group and only include specific tools that you wish to expose.

Once a group is created, mcpjungle returns a unique endpoint for it.

You can then configure your MCP client to use this group-specific endpoint instead of the main gateway endpoint.

You can create a new tool group by providing a JSON configuration file to the create group command.

You must specify a unique name for the group and define which tools to include using one or more of the following fields:
- included_tools: List specific tool names to include (e.g., ["filesystem__read_file", "time__get_current_time"])
- included_servers: Include ALL tools from specific MCP servers (e.g., ["time", "deepwiki"])
- excluded_tools: Exclude specific tools (useful when including entire servers)

Here is an example of a tool group configuration file (claude-tools-group.json):

{

  "name": "claude-tools",

  "description": "This group only contains tools for Claude Desktop to use",

  "included_tools": [

    "filesystem__read_file",

    "deepwiki__read_wiki_contents",

    "time__get_current_time"

  ]

}

This group exposes only 3 handpicked tools instead of all available tools.

You can currently perform operations like listing all groups, viewing details of a specific group and deleting a group.

You can list and invoke tools within specific groups using the --group flag:

mcpjungle list tools --group claude-tools

mcpjungle invoke filesystem__read_file --group claude-tools --input '{"path": "README.md"}'
``

Limitations 🚧
1. Currently, you cannot update an existing tool group. You must delete the group and create a new one with the modified configuration file.
2. In enterprise` mode, currently only an admin can create a Tool Group. We're working on allowing standard Users to create their own groups as well.