Skip to main content
Enterprise mode adds authentication and access control to mcpjungle. These commands are used to bootstrap an enterprise deployment and manage who or what can connect to it. Use the governance guides for the full operational model:
Commands on this page require the server to be running in enterprise mode with mcpjungle start --enterprise.
Treat mcpjungle <command> --help as the authoritative source for current flags. This page keeps the important setup flow, examples, and config patterns.

init-server

Initializes a fresh enterprise server.
Run this once against a new enterprise deployment. It creates the first admin user, generates the admin access token, and stores the server URL and token in ~/.mcpjungle.conf.
This is a one-time bootstrap step. Store the generated admin credentials securely.

login

Stores an existing access token in ~/.mcpjungle.conf so the CLI can authenticate future requests.
Example:
This is what regular users run after an administrator creates their account and shares a token with them.

create mcp-client

Creates an authenticated MCP client identity.
Common flags:
--allow
string
Comma-separated allow list of MCP server names. Example: --allow "github,jira".
--access-token
string
Custom token for the client. If omitted, the server generates one and prints it once.
-c / --conf
string
Path to a JSON config file. When provided, the CLI ignores the other flags.
Examples:
Config file example:
You can also load the token from a file:
When creating a client from --conf, you must provide a custom token via access_token or access_token_ref.
--allow "*" gives the client access to all registered MCP servers, including future ones. This is convenient for testing and strongly discouraged in production.
For token supply options and placeholder handling, see Config file reference.

delete mcp-client

Deletes an MCP client and immediately revokes its access to the mcp gateway.
Example:

create user

Creates a standard user account for a human operator.
Examples:
Config file example:
When user creation succeeds, the CLI prints the mcpjungle login <token> command that the user should run locally.
When creating a user from --conf, you must provide a custom token via access_token or access_token_ref.
For token supply options and placeholder handling, see Config file reference.

delete user

Deletes a user and revokes their access to mcpjungle immediately.
Example:

Typical setup flow

1

Start the server in enterprise mode

2

Initialize the server once

3

Register upstream MCP servers

4

Create MCP clients for agents and apps

5

Create user accounts for operators