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 MCP Integration for CrewAI

Connect Avalara to CrewAI through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write Bearer token auth

Submit Avalara feedback View package source

Connect Avalara to CrewAI

Expose KosmoKrator integrations to CrewAI workers as scoped local tools.

Wrap kosmo integrations:call for specific tasks or connect workers to a local MCP gateway. The gateway is local, scoped to this integration, and starts with --write=deny so CrewAI can inspect read-capable tools without receiving write access by default.

Avalara MCP Config for CrewAI

Use per-worker integration scopes to avoid giving every worker every tool.

{
  "mcpServers": {
    "kosmokrator-avalara": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=avalara",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=avalara --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Avalara instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Avalara Tools Visible to CrewAI

CrewAI sees stable MCP tool names generated from the Avalara integration catalog.

MCP tool	Source function	Type	Description
`integration__avalara__avalara_list_transactions`	`avalara.avalara_list_transactions`	Read	List transactions from Avalara. Supports filtering by date, status, and other criteria with pagination.
`integration__avalara__avalara_get_transaction`	`avalara.avalara_get_transaction`	Read	Retrieve details of a single transaction in Avalara by its ID.
`integration__avalara__avalara_create_transaction`	`avalara.avalara_create_transaction`	Write	Create a new transaction (sales order or invoice) in Avalara for tax calculation. Requires company code, transaction type, date, and line items.
`integration__avalara__avalara_list_companies`	`avalara.avalara_list_companies`	Read	List companies configured in your Avalara account. Supports filtering and pagination.
`integration__avalara__avalara_get_company`	`avalara.avalara_get_company`	Read	Retrieve details of a single company configured in Avalara by its ID.
`integration__avalara__avalara_list_tax_codes`	`avalara.avalara_list_tax_codes`	Read	List tax codes available in Avalara. Tax codes classify products and services for tax purposes. Supports filtering and pagination.
`integration__avalara__avalara_get_current_user`	`avalara.avalara_get_current_user`	Read	Retrieve the current authenticated Avalara user information.

Related Avalara Pages

Avalara CLIUse direct JSON commands instead of MCP discovery. Avalara MCPFull gateway reference and MCP tool names. KosmoKrator for CrewAIClient-level gateway setup.