Headquarters / Developer tools

KooyaHQ CLI and MCP downloads

Use Headquarters from your terminal and connect a local MCP client to the same organization access boundary. Both commands come in one Node.js package.

Get set up

Your workspace.
From your terminal.

CLI + local MCP server

Latest stable release: v0.5.1Download CLI package Release notes

01 / Install

Choose your operating system

The GitHub release package supports macOS, Windows, and Linux with Node.js 22 or newer. It installs the kooyahq CLI and the kooyahq-mcp local server. Native installers are not available for this release.

Install Node.js 22 or newer, then open Terminal.

npm install --global https://github.com/KooyaPH/kooyahq-console-cli/releases/latest/download/kooya-cli.tgz
kooyahq --version

One package installs both kooyahq and the local kooyahq-mcp server.

Install Node.js 22 or newer, then open PowerShell.

npm install --global https://github.com/KooyaPH/kooyahq-console-cli/releases/latest/download/kooya-cli.tgz
kooyahq --version

One package installs both kooyahq and the local kooyahq-mcp server.

Install Node.js 22 or newer, then open Terminal.

npm install --global https://github.com/KooyaPH/kooyahq-console-cli/releases/latest/download/kooya-cli.tgz
kooyahq --version

One package installs both kooyahq and the local kooyahq-mcp server.

Already use the older GitHub CLI? Its kooyahq-cli package provides the same command names. Remove it with npm uninstall -g kooyahq-cli before installing this Console CLI. Its older profile is not migrated automatically; run kooyahq configure with the organization ID. The new profile replaces the old one only after the credential has been validated.

02 / Connect

Create a credential and configure the CLI

Get a credential

Console operators create CLI credentials in their Console account. Headquarters members create theirs in Headquarters Account settings. Copy the secret when it is shown: it cannot be recovered later.

Select your organization

Both credential types require the organization ID. Headquarters members can copy it beside their CLI credentials. Console operators can find the target organization UUID in its Console detail page URL. Use it alongside the access key ID and secret.

Connect and try a read

Run the interactive setup, then verify your account before listing projects. At the Base URL prompt, keep the production default https://console.hq.kooyaai.com for production credentials. For staging credentials, enter https://stage-console.hq.kooyaai.com. Enter secrets only in the CLI prompt; do not paste them into a shell command or MCP configuration.

kooyahq configure
kooyahq auth whoami --output json
kooyahq projects list --all --output json

03 / Update

Check for CLI updates

Updates are explicit: run a command when you are ready. A global installation can download and install the package from GitHub Releases after verifying its SHA-256 digest. Source and temporary installs receive manual installation guidance. Your local credential profile stays in place.

kooyahq update --check
kooyahq update

After an update, run kooyahq mcp doctor --client codex for your configured client.

04 / MCP

Connect a local MCP client

The package includes a local stdio MCP server. After kooyahq configure, install its integration for Codex, Cursor, Claude Code, Gemini CLI, or Google Antigravity, then restart that client.

kooyahq mcp install --client codex
kooyahq mcp doctor --client codex
kooyahq mcp doctor --client codex --online

Replace codex with cursor, claude, gemini, or antigravity for your installed client. The offline doctor checks the local MCP handshake; --online also checks your configured account.

Browser-hosted MCP clients cannot start this local server. They need a separately secured remote gateway.