OFFICIAL RELEASE · v1.0.1

Avola Agent CLI & MCP

A zero-dependency command-line client and local stdio MCP server for AI agents, server automations and reseller systems. Both use the Avola API key created in your own account.

Avola-owned API keysJSON outputLocal stdio MCPNode.js 18+

1. Install

curl -fsSL https://avola.uk/agent/avola-agent.mjs \
  -o avola-agent.mjs
node avola-agent.mjs version

The CLI has no package dependencies and does not modify your system.

2. Authenticate

export AVOLA_API_KEY="avola_live_YOUR_KEY"
node avola-agent.mjs doctor

Keep the key secret. Use an environment secret or secret manager. Do not place it in prompts, browser code or repositories.

Commands

CommandPurpose
services --search youtubeRead and filter the current service catalog.
balanceRead the linked Avola account balance.
order --service ID --link URL --request-id IDPlace an order. Use a unique request ID to prevent duplicate submissions.
status ORDER_ID [ORDER_ID ...]Read up to 100 order statuses.
doctorVerify the key, API connection, catalog and balance access.

Agent usage

Every successful result is JSON on stdout. Every error is JSON on stderr with a non-zero exit code, so agents can reliably branch, retry or stop.

node avola-agent.mjs services --category "X / Twitter"
node avola-agent.mjs status AVO20260714ABCD

Local MCP server

Download the release archive, then configure your MCP client to launch node /absolute/path/avola-mcp.mjs with AVOLA_API_KEY in the process environment.

{
  "command": "node",
  "args": ["/absolute/path/avola-mcp.mjs"]
}

avola_create_order is a dry run unless confirm is the JSON boolean true. No payment or top-up tools are exposed.

Safety boundary

The key can access only its linked Avola balance and orders. Responses do not expose supplier identities, supplier IDs, supplier rates, internal costs, credentials or admin notes.

Agent-readable integration guide · llms.txt