The mcpjungle binary serves two roles: it runs the gateway server and acts as a client for managing everything registered 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.
| Flag | Type | Default | Description |
|---|
--registry | string | http://127.0.0.1:8080 | Base URL of the MCPJungle registry server. |
--help | — | — | Print help for the current command and exit. |
--version / -v | — | — | Print version information and exit. |
--registry flag precedence order is: explicit flag value → registry_url in the config file → built-in default.
If you set --registry explicitly but your config file does not yet have a registry_url entry, the CLI prints a tip reminding you to persist the URL. Use mcpjungle login or manually edit ~/.mcpjungle.conf to avoid passing the flag every time.
Config file
The CLI reads ~/.mcpjungle.conf on startup. The file is YAML and supports two fields:
registry_url: http://your-server:8080
access_token: your-access-token
| Field | Description |
|---|
registry_url | URL of the MCPJungle server. Overrides the --registry default. |
access_token | Bearer token sent with every request. Required in enterprise mode. |
mcpjungle init-server and mcpjungle login. You can also create or edit it by hand.
Available commands
Commands are grouped into Basic (everyday operations) and Advanced (enterprise and power-user features).
Basic commands
| Command | Description |
|---|
start | Start the MCPJungle HTTP server and MCP gateway. |
register | Register an MCP server with the gateway. |
list | List servers, tools, prompts, resources, groups, clients, and users. |
usage | Show input schema and usage information for a tool. |
invoke | Call a registered tool and print its output. |
deregister | Remove an MCP server from the registry. |
version | Print CLI and server version information. |
Advanced commands
| Command | Description |
|---|
get | Retrieve a prompt template or tool group details. |
disable | Disable tools, prompts, or entire servers globally. |
enable | Re-enable previously disabled tools, prompts, or servers. |
create | Create tool groups, MCP clients, or users. |
delete | Delete tool groups, MCP clients, or users. |
update | Update tool groups, MCP client tokens, or user tokens. |
init-server | Initialize the server in enterprise mode (one-time setup). |
login | Authenticate and store your access token locally. |
Running the CLI in Docker or Kubernetes
When the MCPJungle server runs in a container, you can still use the CLI from outside by pointing --registry at the exposed port:
mcpjungle --registry http://localhost:8080 list servers
mcpjungle --registry http://mcpjungle.default.svc.cluster.local:8080 list tools
http://127.0.0.1:8080 works without any extra flags.
The CLI binary is not included in the standard MCPJungle Docker image. Install it on your local machine or in a separate container. See the Installation page for options. 