mcpjungle binary serves two roles: it runs the gateway server and acts as a client for managing everything in that server.
Every subcommand talks to the registry over HTTP, so you can run the CLI on any machine that can reach the server — your laptop, a CI runner, or inside the same container.
Global flags
These flags are accepted by every command and subcommand.
The
--registry flag precedence order is: explicit flag value → registry_url in the config file → built-in default.
Config file
On startup, the CLI attempts to read.mcpjungle.conf in your home directory.
The file is YAML and contains the following fields:
~/.mcpjungle.conf
In enterprise mode, this file gets created automatically when you initialise mcpjungle or login using your CLI.