Starling CLI · Source-available · BSL 1.1

Connect Starling MCP.

There is no public GitHub tarball. Point your MCP client at https://mcp.warbleoss.org. Then Fitment or Murmuration. 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

Claude Desktop / Cursor — hosted MCP (works today)

{
  "mcpServers": {
    "warble": {
      "url": "https://mcp.warbleoss.org"
    }
  }
}

No public Starling tarball. Point the client at mcp.warbleoss.org (list_pods, logs, cluster tools). Doctor is an SRE agent, not a phone agent.

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: Reachable: https://mcp.warbleoss.org

Prefer not to host it yourself?

Point your agent at our hosted MCP at https://mcp.warbleoss.org. 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.