---
title: "CLI command reference"
description: "Information about how to use the mcpjungle CLI"
---

The `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.

| 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. |

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:

```yaml ~/.mcpjungle.conf
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` | Auth token that represents the user, sent with every CLI request. Required in enterprise mode only. |

In enterprise mode, this file gets created automatically when you initialise mcpjungle or login using your CLI.
