We're excited to announce that the Stigg CLI is now available in Public Beta.

🆕 What’s new

You can now interact with the Stigg REST API directly from your terminal using our new Command Line Interface (CLI). The Stigg CLI acts as a lightweight wrapper, allowing developers to query environments, list customers, retrieve subscriptions, and check entitlements without having to write raw HTTP requests or custom scripts.

⭐️ Why it matters

Developers need the right tools for different workflows. While our recently launched MCP Server allows you to manage Stigg using natural language, the Stigg CLI is built for speed, precision, and automation.

Understanding when to use which tool can significantly speed up your development process:

• When to use the Stigg CLI: The CLI is perfect for deterministic, programmatic workflows. It is the go-to tool for scripting automated administrative tasks, integrating Stigg commands into your CI/CD pipelines, or executing quick, repeatable queries directly from your terminal (e.g., verifying a specific customer's entitlement or listing all active plans). It requires no AI context and gives you explicit control over your environment.
• When to use the MCP Server: The MCP Server is designed for AI-driven development. It is best used within AI assistants like Cursor or Claude Desktop when you want to explore the API, scaffold code, or handle complex testing scenarios using natural language prompts without leaving your IDE.

Together, they provide comprehensive developer coverage, ensuring you can integrate and manage your pricing infrastructure securely and efficiently.

⚒️ Get started

Getting started with the CLI is as easy as 1-2-3:

1. Install the CLI via Homebrew or Go.
2. Authenticate using your environment specific API-key.
3. Use - query and manage your Stigg environments via CLI commands

For more details, check out the Stigg CLI documentation.