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 Headless Automation

Use the Avalara CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Bearer token auth

Submit Avalara feedback View package source

Avalara CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Avalara CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Avalara CLI for Headless Automation
kosmokrator integrations:configure avalara --set access_token="$AVALARA_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call avalara.avalara_list_transactions '{"top":1,"skip":1,"filter":"example_filter","orderBy":"example_orderBy"}' --json

Discovery Before Execution

Agents and scripts can inspect Avalara docs and schemas 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

Useful Avalara CLI Functions

Function	Type	Parameters	Description
`avalara.avalara_list_transactions`	Read	top, skip, filter, orderBy	List transactions from Avalara. Supports filtering by date, status, and other criteria with pagination.
`avalara.avalara_get_transaction`	Read	id	Retrieve details of a single transaction in Avalara by its ID.
`avalara.avalara_create_transaction`	Write	companyCode, type, date, code, customerCode, lines, addresses, commit, description	Create a new transaction (sales order or invoice) in Avalara for tax calculation. Requires company code, transaction type, date, and line items.
`avalara.avalara_list_companies`	Read	top, skip, filter	List companies configured in your Avalara account. Supports filtering and pagination.
`avalara.avalara_get_company`	Read	id	Retrieve details of a single company configured in Avalara by its ID.
`avalara.avalara_list_tax_codes`	Read	top, skip, filter	List tax codes available in Avalara. Tax codes classify products and services for tax purposes. Supports filtering and pagination.
`avalara.avalara_get_current_user`	Read	none	Retrieve the current authenticated Avalara user information.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Avalara CLI Pages

CI Avalara CLI for CI. Cron Jobs Avalara CLI for cron jobs. Shell Scripts Avalara CLI for shell scripts. Coding Agents Avalara CLI for coding agents.