CLI

The Aura CLI is the command-line interface for working with AuraBoot projects. It is useful for local development, plugin validation, plugin publishing, runtime checks, and automation scripts.

Common commands

aura login
aura status
aura plugin validate plugins/my-plugin
aura plugin publish plugins/my-plugin --yes
aura query <modelCode>
aura exec <commandCode>

Authentication

For interactive use:

aura login

For scripts and CI, use a token:

export AURA_TOKEN="<jwt>"
aura status

Common environment variables:

Health check

aura status

Use this before plugin import or test automation. It should confirm the backend is reachable and the token is valid.

Plugin workflow

aura plugin validate plugins/project-tracker
aura plugin publish plugins/project-tracker --yes

Validation should run before publish. It catches resource reference problems earlier than manual UI testing.

Query and command execution

Use query commands to inspect data:

aura query crm_lead --limit 10

Use command execution to test backend behavior without clicking through the UI. Command codes are namespace:verb_noun, and field values are passed with repeatable --set flags (key=value, or key:type=value for int / float / bool / json / null):

aura exec crm:create_lead --set lead_name="Acme" --set source="website"

Agent-friendly output

For automation and AI-agent workflows, prefer JSON output. The global --format json flag (or --agent-mode for compact agent-optimized output) is easier to parse and less brittle than the default table output.

aura status --format json
aura query crm_lead --format json

MCP server

AuraBoot can expose runtime tools to MCP-compatible clients:

aura mcp serve

Use this only with a properly authenticated environment. Tool calls should remain tenant-scoped and auditable.

Troubleshooting

Next steps

• Plugin Development
• Config-only Plugins
• REST API