AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in

CLI reference

The agentstack CLI is the fastest way to discover, install, and publish.

Commands

agentstack login [--token <t>]  Sign in via your browser (or paste a token)
agentstack whoami              Show the signed-in user + orgs
agentstack stats [--platform]  Your seller stats (or platform stats for super admins)
agentstack search [query]      Browse / search the catalog
agentstack info <slug>          Show listing details
agentstack add <slug>           Install (alias: install)
agentstack remove <slug>        Uninstall
agentstack list                Installed listings
agentstack update [slug]       Update to the latest entitled version
agentstack publish <path>       Publish (triggers the security scan)

Logging in

agentstack login opens your browser, signs you in, and stores a long-lived token at ~/.agentstack/config.json: no token to copy. For headless/CI, pass one directly with --token <token>.

Checking your stats

agentstack stats               # installs, revenue, conversion, usage: last 30 days
agentstack stats --json        # machine-readable
agentstack stats --platform    # platform-wide totals (super admins only)

Options

  • --client claude|cursor: target agent client (default: claude)
  • --global: install at user scope instead of the project
  • --json: machine-readable output (search/info/list/whoami/stats)
  • --platform: (stats) platform-wide stats, super admins only
  • --token <token>: (login) paste a token instead of the browser flow

Configuration

Config lives at ~/.agentstack/config.json. Override with environment variables: AGENTSTACK_TOKEN, AGENTSTACK_API_URL, AGENTSTACK_GATEWAY_URL, AGENTSTACK_WEB_URL.

Hosted vs self-run MCP

Self-run servers install as a local npx command. Hosted servers install as a remote endpoint pointed at the AgentStack gateway with your license: usage is metered per call.

Creator toolchain Coming soon

Two commands for building and shipping your own MCP servers are in development. They are not available yet: documented here so you know what's coming. 

agentstack dev [path]          Boot a local sandbox that simulates agent tool calls,
                               injects edge cases, and measures token consumption
agentstack deploy [path]       Package a TypeScript/Python function and deploy it to a
                               hosted, monetized MCP endpoint: one command
  • agentstack dev: run your server against simulated agent traffic locally, see which tool calls fire, and profile token usage before you publish.
  • agentstack deploy: go from a local function to a hosted, metered MCP endpoint without managing infrastructure.

Today, publish an existing package with agentstack publish <path> (triggers the security scan). Want early access to dev / deploy? See the creator guide →