Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.stigg.io/llms.txt

Use this file to discover all available pages before exploring further.

Both the CLI and the MCP server give you programmatic access to Stigg, but they’re optimized for different workflows.
CLIMCP server
Best forScripts, CI/CD, terminal workflowsAI-assisted development in coding assistants
How you interactShell commands with flagsNatural language prompts
RequiresTerminal accessAn AI client that supports MCP (Claude Code, Cursor, etc.)
Deterministic?Yes — you write exact commandsNo — the agent decides which calls to make
Good for automation?Yes — scriptable and pipe-friendlyNo — not designed for unattended automation
Use the CLI when you want direct, predictable control: scripting, CI/CD pipelines, one-off admin tasks, or any situation where you need to know exactly what API call will be made. Use the MCP server when you’re already working inside an AI coding assistant and want to describe what you need in plain English — for example, “show me all customers on the Pro plan who haven’t used any API calls this month.”