Tiger CLI — Tiger Cloud + MCP Server

Practical Notes

• GitHub: 107 stars · 9 forks; pushed 2026-05-11 (verified via GitHub API).
• README includes install scripts for macOS/Linux/WSL and Windows, plus brew install --cask ... and go install ...@latest.
• README quick start includes tiger auth login, tiger service list, and tiger mcp install.

Main

A good “AI + CLI” pattern:

• Keep the CLI as the source of truth (commands are auditable and replayable).
• Let the agent draft the next command, then you review and run it.
• Persist the command history in your runbook so future incidents start from a known baseline.

If you enable the MCP server, treat it like any other privileged integration: limit scope, log tool calls, and rotate credentials.

FAQ

Q: Do I have to use the install script? A: No—README lists multiple options including Homebrew, package managers, and go install.

Q: Can I use it without MCP? A: Yes—the CLI works standalone; MCP is an optional integration.

Q: What should I automate first? A: Read-only commands like listing services and showing config before create/delete operations.