List projects and approved teams
mechasm projects list --json
mechasm teams list --json
projects list shows projects this device can access. teams list shows only teams where this device was approved to create projects. If a team is missing, sign in again and approve project creation for that team. Your account must already belong to the team; ask its owner if you do not have access.
Create a project
mechasm projects create --name "Store QA" --url https://app.example.com --team TEAM_ID
Replace the example URL and TEAM_ID with your values. Project names must be 1–120 characters. --team is optional when exactly one team is approved. Project creation uses an idempotency key. If the result is unknown, retry with the same --idempotency-key KEY shown by the CLI; this prevents duplicate projects.
Use the returned project ID for later commands. The CLI cannot create teams or delete projects.
Manage project variables
Choose a file or standard input for each value. Do not pass secret values as command-line flags.
# Read API_KEY from a file.
mechasm variables set API_KEY --project PROJECT_ID --value-file ./api-key.txt
# Or read PAYMENT_TOKEN from standard input.
printf %s "$PAYMENT_TOKEN_VALUE" | mechasm variables set PAYMENT_TOKEN --project PROJECT_ID --value-stdin
mechasm variables list --project PROJECT_ID
mechasm variables unset OLD_KEY --project PROJECT_ID
Variable writes require project edit access. Each value can be up to 64 KiB. Keys must be 1–255 characters, uppercase, and contain no whitespace. Existing IMAP and VPN integration settings are supported.
Variable values are omitted from command output; list and successful set/unset results show key names only. --value-stdin and --token-stdin both read standard input, so they cannot be used together. Use --value-file when supplying a token through stdin.