Skip to main content
The Endgame CLI is a command-line client for the Endgame MCP endpoint. It lets you call any Endgame tool and script Endgame into your own workflows — no AI assistant required. It’s a good fit for developers, automation, and agent-heavy workflows where you want direct, repeatable access to Endgame from the terminal. If you want an AI assistant (Claude, ChatGPT, Claude Code, or Codex) to use Endgame tools conversationally, see the MCP Server page instead.

​
Installation

The CLI is a Go binary built from the endgame-cli repository. You’ll need Go installed.
The install script builds the binary and installs it to /usr/local/bin (or ~/.local/bin if that isn’t writable). You can also pass a custom install directory: ./install.sh ~/bin. Verify the install:

​
Authentication

Authenticate with your Endgame account via OAuth:
When run interactively, the CLI prompts you to choose a login method:
  • Browser login — opens a browser on this machine and completes the OAuth flow on a localhost callback
  • Device-code login — displays a code you enter in a browser on any device, for remote servers or separate browser sessions
You can also select the mode explicitly:
If the CLI is running on a remote server and you want to use browser mode, forward the callback port first: ssh -L 8788:127.0.0.1:8788 <server>, then run endgame auth login --mode browser --callback-port 8788.
Check your authentication state at any time:
Tokens are stored in ~/.endgame-auth.json and refresh automatically — the CLI reuses the cached access token until it nears expiry, refreshes once before the request, and retries once on an authentication error. There are no auth environment variables to configure.

​
Running Tools

The CLI discovers the tools available to your account at login and caches them locally. Endgame updates its tools periodically, so sync before you start working to make sure you have the latest set:
The CLI also refreshes the cache automatically after login and in the background when it is more than 12 hours old. See your tool set, with full documentation for each tool’s inputs:
Invoke any tool by name, passing its input as JSON via --json or piped stdin:
The exact tool set is discovered from your account, so endgame tools --help always reflects what you can actually call. For a description of each tool, see Available Tools on the MCP Server page.

​
Command Reference

​
Configuration

​
Need Help?

For issues or questions about the Endgame CLI, contact your Endgame administrator or reach out to support@endgame.io.