ComPress Store Agent CLI

Public store-admin install and agent setup kit for the ComPress CLI.

Use this repository when you manage one ComPress store and want a local CLI or an MCP-capable agent, such as Hermes, to work through your store API token.

This repo contains:

• an installable built copy of the compress CLI runtime;
• store-admin onboarding docs;
• sanitized agent skill files for safe CLI and MCP use;
• example profile and MCP configuration snippets with placeholders only.

It does not contain ComPress platform source, platform operator runbooks, tenant data, local credentials, or API tokens.

Install

Requirements:

• Node.js 22 or newer
• npm
• a ComPress store admin account with permission to create store CLI API keys

Current GitHub install:

npm install -g github:lyc-aon/compress-store-agent-cli
compress doctor --json

Preferred package-manager install after the npm package is published:

npm install -g @compress/cli
compress doctor --json

To upgrade a GitHub install, rerun the GitHub install command. To upgrade an npm install, run:

npm install -g @compress/cli@latest

Set Up A Store Profile

Use a separate profile per store.

compress profile set my-store \
  --scope store \
  --environment production \
  --base-url https://your-store.example \
  --use

Create a store CLI token from Admin > API Keys, then load it into your shell without putting it in chat, docs, or shell history:

read -rsp "ComPress store CLI token: " COMPRESS_API_TOKEN; echo
export COMPRESS_API_TOKEN
compress auth token-login --profile my-store --scope store --json
unset COMPRESS_API_TOKEN

Verify the profile and token:

compress auth whoami --profile my-store --scope store --json
compress store token current --profile my-store --json
compress sync --profile my-store

The token is stored profile-scoped in the local ComPress credential store. It is not stored in profiles.json.

Set Up Hermes Or Another MCP Agent

One-command Hermes setup:

compress agent setup hermes --profile my-store --bundle store-manage

Manual MCP server examples:

compress mcp bundles
compress mcp serve --scope store --profile my-store --bundle store-read --readonly
compress mcp serve --scope store --profile my-store --bundle store-content
compress mcp serve --scope store --profile my-store --bundle store-commerce
compress mcp serve --scope store --profile my-store --bundle store-ops
compress mcp serve --scope store --profile my-store --bundle store-manage

store-manage is the default store bundle when no --readonly, --allow, or --deny option is provided. Server-side store RBAC, plugin gates, dry-run, idempotency, confirmation, and audit checks still apply.

Safe Store Operations

Agents should discover the live command surface instead of guessing command lists:

compress commands list --profile my-store --scope store --json
compress commands docs --profile my-store --scope store --search setup
compress commands docs --profile my-store --scope store --plugin commerce-core

For mutating work:

• run a dry-run first when supported;
• pass an idempotency key;
• only pass confirmation text after the human confirms the exact target;
• use Action Authority proposals when direct non-dry-run writes return ACTION_AUTHORITY_REQUIRED.

See:

• Install
• Store Profile And Token
• Agent MCP Setup
• Command Patterns
• Risk Policy
• Troubleshooting
• Agent Skill

Credential Rule

Never paste ComPress API tokens, passwords, refresh cookies, raw credential files, payment credentials, SMTP credentials, or provider secrets into an agent chat or a GitHub issue. If a token is exposed, revoke it in ComPress Admin and create a new one.