@available-core/cli (avc)

The Available Core developer CLI — build and dev-run custom apps (sandboxed UI panels that mount inside your workspace, e.g. the ticket sidebar) and help-center themes (custom colors, fonts, and CSS for your public help center).

Runs anywhere Node.js 20+ runs: macOS, Linux, Windows.

Install

npm install -g @available-core/cli
# or run without installing:
npx @available-core/cli apps dev ./my-app

Commands

avc apps new [dir] --name "My App"      Scaffold a starter app bundle
avc apps dev [dir] [--port 4567] [--https]
                                        Serve a bundle locally for ?avc_apps=
avc apps create --name "My App" [--description d]
                                        Create the app record
avc apps list                           List this brand's apps
avc apps upload <dir> --app <id>        Upload a new draft version
avc apps publish --app <id> --version <id>
                                        Publish a version live
avc themes new [dir] --name "My Theme"  Scaffold a help-center theme
avc themes dev [dir] [--port] [--https] Serve a theme locally for ?avc_theme=
avc themes create --name "My Theme" [--description d]
                                        Create the theme record
avc themes list                         List this brand's themes
avc themes upload <dir> --theme <id>    Upload a new draft theme version
avc themes publish --theme <id> --version <id>
                                        Publish a theme version
avc themes activate --version <id> | --default
                                        Apply a theme (or revert to default)
avc mcp                                 Proxy the workspace MCP server over stdio
avc mcp config                          Print an MCP client config snippet
avc login --host <url> --token <avc_…>  Save host + API key

Use as an MCP server

avc mcp exposes your workspace's MCP tools to any MCP client (Claude Desktop, Cursor, Claude Code) over stdio, using the key from avc login — so the key stays out of the client config. Run avc mcp config for the snippet to paste. Clients that speak remote HTTP MCP can point straight at …/api/mcp instead.

avc apps new and avc apps dev work offline. The rest talk to your workspace and need auth.

Auth

Provide your workspace host + a personal API key (created under your profile → API keys). Resolution order: flags → environment → saved config.

avc login --host https://core.available.dk --token avc_xxxxxxxxxxxxxxxxxxxxxx
# or per-command:
export AVC_HOST=https://core.available.dk
export AVC_TOKEN=avc_xxxxxxxxxxxxxxxxxxxxxx

Write commands (create, upload, publish) require an admin role.

Local dev against real data

avc apps new ./my-app --name "Order Lookup"
avc apps dev ./my-app          # http://localhost:4567

Then open a ticket in your workspace with ?avc_apps=1 (admin only). Edit a file and the panel live-reloads. Use --https if your browser blocks framing http://localhost.

Documentation

Full docs: the Custom apps and Help-center themes sections of your workspace help center.