MiqromanageSupport
Sign in Contact support

The `miqro` CLI

Status: built and runnable from the repo (cli/). Read/identity, control-plane writes (queue approve/reject/cancel, connect, agent run), and the MCP bridge (mcp serve / tools / add / ls / rm) all work today. mcp serve exposes the same command registry the CLI binds — so the CLI and Miqro's MCP surface are provably two faces of one capability core. Read MCP overview alongside this.

See CLI use cases and the end-to-end CLI + integrations walkthrough for practical workflows.

miqro is the command-line and scriptable interface to the Miqro platform — the human/CI counterpart to the agent + MCP surface. Anything an agent can do through a tool, an operator can do through a command, because both run on the same API, the same connector capabilities, and the same approval gate.

One core, three faces

                       capability core
        connectors + HTTP API + the action queue / approval gate
                              │
        ┌──────────────────────┼───────────────────────┐
        ▼                       ▼                        ▼
   miqro CLI               MCP server                MCP client
  humans + CI/CD         agents call in           agents reach out
        └─────────── one shared command surface ───────────┘
  • CLI — you, in a terminal or a CI pipeline.
  • MCP client — an agent reaching out to control external systems (agentic control).
  • MCP server — an external AI client calling into Miqro (roadmap).

They share commands by design. miqro queue approve <id> operates the same approval queue an agent's writes flow into — the human surface and the agent surface share the control plane, not just code.

Install

pipx install miqro          # once published
# or, from the repo:
pipx install ./cli

Authenticate

miqro login                 # opens the Miqro sign-in wall, stores your token
miqro whoami                # shows your role, tenant, and plan entitlement

Credentials resolve in priority order: MIQRO_TOKEN / MIQRO_API_BASE env vars → ~/.miqro/config.toml → a prompt to run miqro login. A separate service mode (X-Internal-Key) exists for CI/operator automation; it's opt-in and never the default.

A few things you can do

# See every system the agents can connect to (the live capability catalog)
miqro connectors ls
miqro connectors show servicenow

# Operate the approval queue — the same gate agent actions pass through
miqro queue ls --status pending_approval
miqro queue approve act_01H...

# Watch the fleet
miqro runs --live
miqro runs tail --agent support_sla_agent

# Connect MCP servers for agentic control  🔒 Enterprise / miqromanage
miqro mcp add github --url https://...
miqro mcp ls

Scripting

Every command takes --json for machine-readable output and exits non-zero on API errors, so it composes in shells and pipelines:

miqro queue ls --status pending_approval --json | jq '.[].id'

What's gated

The CLI itself is open to any signed-in user, scoped to your role and tenant (the same row-level scoping the API enforces). The MCP commands (miqro mcp …) require the Enterprise / miqromanage plan, the same gate as agentic control. agent run requires operator/service credentials.

Next