Can I use Avalara as a CLI?

Yes. KosmoKrator exposes a Avalara CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Avalara through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Avalara tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Avalara credentials stored?

Avalara credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Avalara MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

sales

Avalara CLI for AI Agents

Use the Avalara CLI from KosmoKrator to call Avalara tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

7 functions 6 read 1 write Bearer token auth

Submit Avalara feedback View package source

Avalara CLI Setup

Avalara can be configured headlessly with `kosmokrator integrations:configure avalara`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure avalara --set access_token="$AVALARA_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor avalara --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`access_token`	`AVALARA_ACCESS_TOKEN`	Secret `secret`	yes	Access Token

Call Avalara Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call avalara.avalara_list_transactions '{
  "top": 1,
  "skip": 1,
  "filter": "example_filter",
  "orderBy": "example_orderBy"
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:avalara avalara_list_transactions '{
  "top": 1,
  "skip": 1,
  "filter": "example_filter",
  "orderBy": "example_orderBy"
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs avalara --json
kosmo integrations:docs avalara.avalara_list_transactions --json
kosmo integrations:schema avalara.avalara_list_transactions --json
kosmo integrations:search "Avalara" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Avalara.

`avalara.avalara_list_transactions`

Read read

List transactions from Avalara. Supports filtering by date, status, and other criteria with pagination.

Parameters: top, skip, filter, orderBy

Generic CLI call

kosmo integrations:call avalara.avalara_list_transactions '{"top":1,"skip":1,"filter":"example_filter","orderBy":"example_orderBy"}' --json

Provider shortcut

kosmo integrations:avalara avalara_list_transactions '{"top":1,"skip":1,"filter":"example_filter","orderBy":"example_orderBy"}' --json

`avalara.avalara_get_transaction`

Read read

Retrieve details of a single transaction in Avalara by its ID.

Parameters: id

Generic CLI call

kosmo integrations:call avalara.avalara_get_transaction '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:avalara avalara_get_transaction '{"id":"example_id"}' --json

`avalara.avalara_create_transaction`

Write write

Create a new transaction (sales order or invoice) in Avalara for tax calculation. Requires company code, transaction type, date, and line items.

Parameters: companyCode, type, date, code, customerCode, lines, addresses, commit, description

Generic CLI call

kosmo integrations:call avalara.avalara_create_transaction '{"companyCode":"example_companyCode","type":"example_type","date":"example_date","code":"example_code","customerCode":"example_customerCode","lines":"example_lines","addresses":"example_addresses","commit":true}' --json

Provider shortcut

kosmo integrations:avalara avalara_create_transaction '{"companyCode":"example_companyCode","type":"example_type","date":"example_date","code":"example_code","customerCode":"example_customerCode","lines":"example_lines","addresses":"example_addresses","commit":true}' --json

`avalara.avalara_list_companies`

Read read

List companies configured in your Avalara account. Supports filtering and pagination.

Parameters: top, skip, filter

Generic CLI call

kosmo integrations:call avalara.avalara_list_companies '{"top":1,"skip":1,"filter":"example_filter"}' --json

Provider shortcut

kosmo integrations:avalara avalara_list_companies '{"top":1,"skip":1,"filter":"example_filter"}' --json

`avalara.avalara_get_company`

Read read

Retrieve details of a single company configured in Avalara by its ID.

Parameters: id

Generic CLI call

kosmo integrations:call avalara.avalara_get_company '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:avalara avalara_get_company '{"id":"example_id"}' --json

`avalara.avalara_list_tax_codes`

Read read

List tax codes available in Avalara. Tax codes classify products and services for tax purposes. Supports filtering and pagination.

Parameters: top, skip, filter

Generic CLI call

kosmo integrations:call avalara.avalara_list_tax_codes '{"top":1,"skip":1,"filter":"example_filter"}' --json

Provider shortcut

kosmo integrations:avalara avalara_list_tax_codes '{"top":1,"skip":1,"filter":"example_filter"}' --json

`avalara.avalara_get_current_user`

Read read

Retrieve the current authenticated Avalara user information.

Parameters: none

Generic CLI call

kosmo integrations:call avalara.avalara_get_current_user '{}' --json

Provider shortcut

kosmo integrations:avalara avalara_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`avalara.avalara_list_transactions`

List transactions from Avalara. Supports filtering by date, status, and other criteria with pagination.

Operation: Read read
Schema command: kosmo integrations:schema avalara.avalara_list_transactions --json

Parameter	Type	Required	Description
`top`	integer	no	Number of transactions to return per page (default 20).
`skip`	integer	no	Number of records to skip for pagination.
`filter`	string	no	OData filter expression, e.g. "status eq 'Committed'" or "date ge 2024-01-01".
`orderBy`	string	no	OData order-by expression, e.g. "date desc".

`avalara.avalara_get_transaction`

Retrieve details of a single transaction in Avalara by its ID.

Operation: Read read
Schema command: kosmo integrations:schema avalara.avalara_get_transaction --json

Parameter	Type	Required	Description
`id`	string	yes	The transaction ID (can be the Avalara transaction ID or the code).

`avalara.avalara_create_transaction`

Create a new transaction (sales order or invoice) in Avalara for tax calculation. Requires company code, transaction type, date, and line items.

Operation: Write write
Schema command: kosmo integrations:schema avalara.avalara_create_transaction --json

Parameter	Type	Required	Description
`companyCode`	string	yes	The company code for the transaction.
`type`	string	no	Transaction type: "SalesOrder" or "SalesInvoice" (default "SalesOrder").
`date`	string	no	Transaction date in YYYY-MM-DD format. Defaults to today.
`code`	string	no	A unique reference code for this transaction.
`customerCode`	string	no	The customer code for the transaction.
`lines`	array	yes	Array of line items. Each line should include "amount", "quantity", and optionally "taxCode", "description".
`addresses`	object	no	Address information for tax calculation, including "shipFrom" and "shipTo" with "city", "region", "country", "postalCode".
`commit`	boolean	no	Whether to commit the transaction immediately (default false).
`description`	string	no	Description of the transaction.

`avalara.avalara_list_companies`

List companies configured in your Avalara account. Supports filtering and pagination.

Operation: Read read
Schema command: kosmo integrations:schema avalara.avalara_list_companies --json

Parameter	Type	Required	Description
`top`	integer	no	Number of companies to return per page (default 20).
`skip`	integer	no	Number of records to skip for pagination.
`filter`	string	no	OData filter expression, e.g. "isDefault eq true".

`avalara.avalara_get_company`

Retrieve details of a single company configured in Avalara by its ID.

Operation: Read read
Schema command: kosmo integrations:schema avalara.avalara_get_company --json

Parameter	Type	Required	Description
`id`	string	yes	The company ID in Avalara.

`avalara.avalara_list_tax_codes`

List tax codes available in Avalara. Tax codes classify products and services for tax purposes. Supports filtering and pagination.

Operation: Read read
Schema command: kosmo integrations:schema avalara.avalara_list_tax_codes --json

Parameter	Type	Required	Description
`top`	integer	no	Number of tax codes to return per page (default 20).
`skip`	integer	no	Number of records to skip for pagination.
`filter`	string	no	OData filter expression, e.g. "isActive eq true" or "taxCode eq 'P0000000'".

`avalara.avalara_get_current_user`

Retrieve the current authenticated Avalara user information.

Operation: Read read
Schema command: kosmo integrations:schema avalara.avalara_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.