Microtica CLI
Install the Microtica CLI and drive your projects, environments, apps, pipelines, and logs from the terminal or an AI agent. Get set up in minutes.
The microtica CLI brings the Microtica platform to your terminal. List and deploy environments, roll out applications to Kubernetes, trigger pipelines, and stream build and deployment logs — all without leaving your shell or your editor's AI agent.
The CLI is a thin wrapper over the Microtica SDK. Every command calls the same typed client the SDK exposes, so behavior stays identical whether you script against the SDK or run a one-off command.
Install
The CLI ships as the @microtica/cli npm package and installs a single microtica binary. You need Node.js 18 or newer.
npm install -g @microtica/cli
microtica --versionRun microtica --help to list every command, and microtica <command> --help for the flags on any one.
Quickstart
Authenticate once, point the CLI at a project, and you're ready to go.
# 1. Store your API key
microtica login --token mic_…
# 2. Set a default project so you don't repeat --project everywhere
export MICROTICA_PROJECT_ID=<project-id>
# 3. Confirm who you are and that the API is reachable
microtica whoami
# 4. List the environments in your project
microtica env listmicrotica project list shows every project your credential can access, so you can grab a project id for step 2.
What you can do
Authentication
Create an API key, log in, and configure the CLI with environment variables.
Output & queries
Switch to JSON, filter responses with JMESPath, and read the error and exit-code conventions.
Command reference
Every command for projects, environments, apps, pipelines, components, Git, and logs.
Use with AI agents
Point Claude Code, Cursor, or any harness at the CLI's built-in agent reference.
Next steps
Automated saving schedules
Cut AWS costs with automated saving schedules in Microtica: start and stop EC2 and RDS instances on a schedule to save up to 60% in non-production environments.
Authenticate the CLI
Create a Microtica API key in the console, log in to the CLI, see where credentials are stored, and configure the CLI with environment variables.