TaxJar MCP integration for AI agents.
Connect AI agents to TaxJar through 21 structured actions, including list customers, create customer, create refund transaction, and calculate sales tax for…
- ACTION CONTRACTS
- 21
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the TaxJar integration exposes
The TaxJar Agent App exposes 21 provider-backed actions for finance and data work. Its current contract lets an authorized agent list taxjar customer identifiers, create a taxjar customer for exemption management, and create a taxjar refund transaction. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected TaxJar account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real TaxJar capabilities.
Showing 12 of 21 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_customersREADList TaxJar customer identifiers.
INPUTS: page / per_page
create_customerWRITECreate a TaxJar customer for exemption management.
INPUTS: customer_id / exemption_type / name / country / state
create_refund_transactionHIGH IMPACTCreate a TaxJar refund transaction.
INPUTS: transaction_id / transaction_date / transaction_reference_id / provider / to_country
calculate_sales_tax_for_orderREVIEWCalculate TaxJar sales tax for an order.
INPUTS: from_country / from_zip / from_state / from_city / from_street
create_order_transactionWRITECreate a TaxJar order transaction for reporting and filing.
INPUTS: transaction_id / transaction_date / provider / to_country / to_zip
delete_customerHIGH IMPACTDelete a TaxJar customer by identifier.
INPUTS: customer_id
delete_order_transactionHIGH IMPACTDelete a TaxJar order transaction by identifier.
INPUTS: transaction_id
delete_refund_transactionHIGH IMPACTDelete a TaxJar refund transaction by identifier.
INPUTS: transaction_id
list_nexus_regionsREADList TaxJar nexus regions for the account.
list_order_transactionsREADList TaxJar order transaction identifiers within a date range.
INPUTS: from_transaction_date / to_transaction_date / provider
list_refund_transactionsHIGH IMPACTList TaxJar refund transaction identifiers within a date range.
INPUTS: from_transaction_date / to_transaction_date / provider
list_tax_categoriesREADList TaxJar product tax categories and codes.
INPUT CONTRACTS
Know what the action needs before it runs.
list_customers
pageOPTIONAL- Page number to retrieve.
per_pageOPTIONAL- Number of customers per page.
create_customer
customer_idREQUIRED- TaxJar customer identifier.
exemption_typeREQUIRED- Customer exemption type, such as wholesale, government, non_profit, or other.
nameREQUIRED- Customer name.
countryOPTIONAL- Customer country code, using ISO 3166-1 alpha-2 format.
stateOPTIONAL- Customer state or province.
create_refund_transaction
transaction_idREQUIRED- Unique refund transaction identifier.
transaction_dateREQUIRED- Refund transaction date in YYYY-MM-DD format.
transaction_reference_idREQUIRED- Original order transaction identifier.
providerOPTIONAL- Optional source provider name.
to_countryREQUIRED- Destination country code, using ISO 3166-1 alpha-2 format.
calculate_sales_tax_for_order
from_countryREQUIRED- Origin country code, using ISO 3166-1 alpha-2 format.
from_zipREQUIRED- Origin ZIP or postal code.
from_stateREQUIRED- Origin state or province.
from_cityOPTIONAL- Origin city.
from_streetOPTIONAL- Origin street address.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Customers
List TaxJar customer identifiers. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_customersControl Create Customer
Create a TaxJar customer for exemption management. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_customerVerify with Create Customer
Create a TaxJar customer for exemption management. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_customerSAFETY BOUNDARY
Operate TaxJar with explicit limits
- Authorize TaxJar with API key and grant only the provider access required by the selected actions.
- 11 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `create_refund_transaction`, `delete_customer`, and `delete_order_transaction` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in TaxJar rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the TaxJar task completed successfully.
CONNECTION MODEL
API key
TaxJar API token sent as a Bearer token. Get it from TaxJar under Account > TaxJar API.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 7
- REVIEW SIGNALS
- 6
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by TaxJar.