Starling CLI · Open source · Apache 2.0

Install Starling.

Install the binary, then starling login. Your token lands in the config file automatically — no paste-the-key dance.

Free: local MCP over your own kubeconfig (starling mcp). Credits: scan_manifest (3), cluster.* hosted (1–2), scan_cluster (10).

Configure your IDE Validate below

Direct binary (Apple Silicon · M1/M2/M3/M4)

curl -L https://github.com/warble-tech/starling/releases/download/v0.1.0/starling_0.1.0_macOS_arm64.tar.gz \
  | tar xz -C /usr/local/bin starling
starling --version

Signed binary from github.com/warble-tech/starling/releases. Apache-2.0.

Direct binary (Intel)

curl -L https://github.com/warble-tech/starling/releases/download/v0.1.0/starling_0.1.0_macOS_amd64.tar.gz \
  | tar xz -C /usr/local/bin starling

Homebrew (coming with v0.1.0)

brew tap warble-tech/tap
brew install starling

Tap is auto-published by GoReleaser on tag. Works after the first v0.1.0 release lands.

Validate your install

Five commands, five checks.

Each step should take seconds. If any fails, check contact with the output.

1. Confirm the binary works

starling version

Expected: starling v0.1.0 (commit …, built …)

2. Sign in (opens your browser)

starling login

Expected: ✓ Logged in as you@example.com (free)

3. Check balance + plan

starling whoami

Expected:

Account : you@example.com
Plan    : free
Credits : 0

4. Run a local MCP against your cluster (free)

starling mcp --mode=readonly --transport=stdio

Expected: stdio listening; point Claude Desktop at this command

5. Diagnose any issues

starling doctor

Expected: 6 checks: credentials, kubeconfig, kubectl, warblecloud.com, ops-mcp, whoami

Prefer not to host it yourself?

Point your agent at our hosted MCP at https://ops-mcp.warblecloud.com/mcp. Pay-as-you-go credits, starting from $1.

Buy credits Open the portal

Binaries are Go modules — audit the source on GitHub. Report issues at /issues.