Can AI agents automate Avalara Returns?

Avalara Returns is automatable today through the Managed Returns GraphQL API and a first-party hosted MCP server. This record is Avalara Returns filing and remittance, including the Managed Returns, VAT, Excise, MyLodge, and property-tax domains exposed by the Returns MCP. Avalara AvaTax and E-Invoicing and Live Reporting are separate products. The opened U.S. and Canada guide uses the sandbox GraphQL endpoint https://returns-api.sbx.avalara.com/graphql. Callers exchange an account id and license key for a JWT at https://ai-sbx.avlr.sh/connect/token with grant_type=client_credentials, then send Authorization Bearer. Firm credentials provision and link client accounts. Client credentials manage companies, filing calendars, filings, and notices. Avalara provisions the firm account before integration starts. The hosted MCP server at https://mcp.avalara.com/returns does not use the OAuth2 flow. It requires that JWT in an Authorization bearer header and a mandatory business domain on every request, using X-Returns-Tools or the tools query parameter. Named domains include us-returns, vat-returns, propertytax, mylodge, and excise. Omitting the domain blocks tool calls. The opened tool table includes filing calendars, filings, liability reports, filing attachments, approve_filings_returns, and funding power-of-attorney calls, plus MyLodge, property-tax, VAT, and Excise tools. A separate Returns SDK and a first-party CLI were not established. iPaaS connector catalogs were not opened. Computer-use viability is unassessed. API and MCP both score 7. API is the best path because it is the documented filing contract and does not add the MCP domain header on top of the same license-key JWT.

Best path today: api · Overall automatability: 7/10