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.
~/.mcpjungle.conf.
login
Stores an existing access token in ~/.mcpjungle.conf so the CLI can authenticate future requests.
create mcp-client
Creates an authenticated MCP client identity.
Comma-separated allow list of MCP server names. Example:
--allow "github,jira".Custom token for the client. If omitted, the server generates one and prints it once.
Path to a JSON config file. When provided, the CLI ignores the other flags.
When creating a client from
--conf, you must provide a custom token via access_token or access_token_ref.delete mcp-client
Deletes an MCP client and immediately revokes its access to the mcp gateway.
create user
Creates a standard user account for a human operator.
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.delete user
Deletes a user and revokes their access to mcpjungle immediately.
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
