Command line

Use agentcentral from the terminal

The agentcentral CLI gives scripts, cron jobs, CI steps, and local MCP clients the same Amazon seller tools your agent uses in chat. Use it to list tools, call them with JSON input, bridge clients that need a local command, and check account health without pasting keys into conversations.

When to use the CLI

Connect an agent directly when it can use a remote MCP URL and an authorization header. Use the CLI when the work starts from your terminal or from software that can only launch a local command.

Connect directly when	Use the CLI when
Claude, ChatGPT, OpenClaw, Hermes, or another client can connect to `https://mcp.agentcentral.to/mcp`	A shell script, cron job, CI step, or local process needs to run the same tools on a schedule
The client can send an `Authorization` header or use a signed connector URL from the dashboard	The client can only start a local MCP command, so it needs`agentcentral mcp serve`
You want the model to choose tools during a conversation	You want predictable JSON output, file output, and shell exit codes

What you can do from the terminal

Inspect

List, describe, and call tools

Use agentcentral tools list, tools describe, tools schema, and tools call to run account-scoped tools from a script or one-off shell command.

Bridge

Connect local MCP clients

Use agentcentral mcp serve when a client expects a local stdio MCP server instead of a remote URL with headers. See the bridge guide.

Verify

Check account and connection health

Use agentcentral doctor and agentcentral account info before automation or writes. Both report the resolved account and marketplace without printing the raw key.

Same key, same limits

The CLI does not create a second access path

It uses the same ac_live_ API key you create in the dashboard. The key's dashboard scope controls which domains, marketplaces, and write actions the CLI can use. If a key is read-only in the dashboard, a local flag cannot turn it into a write key.

Install

The CLI is published on npm as @agentcentral/cli. Install it globally to get the agentcentral command:

npm install -g @agentcentral/cli
agentcentral --version

You can also run it with npx @agentcentral/cli without installing, which is handy for one-off commands and CI jobs. Full setup is in the install guide.

Authenticate for automation

For scripts, set AGENT_CENTRAL_API_KEY to an ac_live_ key from the dashboard Keys tab. The CLI never accepts a key as a flag value, which keeps it out of shell history and process listings.

export AGENT_CENTRAL_API_KEY="ac_live_..."
agentcentral doctor
agentcentral tools list --format table

For stored login, named profiles, keychain behavior, and precedence, see auth and profiles.

Where to go next

Install — install the CLI from npm or run it with npx.
Auth and profiles — choose how scripts and local sessions get a key.
Local MCP bridge — connect clients that need a local command.
Automation — run tools from cron, CI, and shell scripts.
Write safety — preview changes and submit safely.
Security — understand what is stored locally and what is enforced by agentcentral.