AgentTax MCP Server
OfficialAgentTax MCP Server calculates and tracks US sales/use tax for AI-agent transactions, and logs digital-asset trades for capital-gains reporting.
calculate_tax— full sales/use tax calculation (buyer or seller role) returning tax amount, rate, jurisdiction, audit trail and advisories; takesamount,buyer_state,transaction_type,counterparty_id, plus optionalwork_type,is_b2b,buyer_zip,seller_remitting.track_payment— records a payment you received (Stripe, x402, direct) and returns your tax liability, auto-classifying from thedescription; acceptspayment_idfor dedup.log_trade— logs buy/sell trades and returns realized gain/loss with cost basis (fifo/lifo/specific_id, lot IDs, resident state).get_rates— state sales tax rates and digital-goods/SaaS taxability for one state or all 51 jurisdictions, with compact/verified/explanatory formats.configure_nexus— sets the states where you have economic nexus (required for non-zero seller tax results).check_health— checks API health, available endpoints and pricing tiers.All exposed tools are compute/read-style (
taskSupport: forbidden); the README notes further tools (bulkingest_transactions,list_transactions, nexus queries,export_1099_da, local rates, pricing) beyond this schema.
Allows automatic tax tracking via Stripe webhooks, processing payment events to calculate and log sales tax liabilities.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AgentTax MCP Server Track a $49 payment from Texas."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AgentTax MCP Server
Tax compliance for MCP tool developers and AI agents, powered by AgentTax.
For MCP tool developers
If you build MCP tools that charge for usage, you have sales tax obligations in states where your buyers are located. Most payment processors don't handle this correctly for digital services.
Add AgentTax to your MCP setup and call track_payment after every payment. That's it.
{
"mcpServers": {
"agenttax": {
"command": "npx",
"args": ["@agenttax/mcp-server"],
"env": {
"AGENTTAX_API_KEY": "atx_live_your_key"
}
}
}
}After a payment:
track_payment({
amount: 49.00,
buyer_state: "TX",
buyer_zip: "78701",
description: "MCP API access — monthly subscription",
payment_id: "pi_stripe_abc123",
source: "stripe"
})Returns your tax liability, compliance status, and logs it to your account. All transactions are viewable in your AgentTax dashboard.
Related MCP server: AgentaOS
Stripe webhook (fully automated)
For fully automatic tax tracking without calling any tool manually, point your Stripe webhook to AgentTax:
In Stripe Dashboard → Developers → Webhooks, add an endpoint:
https://agenttax.io/api/v1/webhooks/stripe?key=atx_live_YOUR_KEYSelect events:
payment_intent.succeeded,checkout.session.completed,invoice.paid,charge.succeededOptional: set
metadata.work_typeon your Stripe products (compute|research|content|consulting|trading) for precise tax classification
Every payment is automatically classified, taxed, and logged. No code changes required.
Requires a billing address on the Stripe payment. Enable full address collection in your Stripe Checkout settings.
Install
Claude Code
claude mcp add agenttax -e AGENTTAX_API_KEY=atx_live_your_key -- npx -y @agenttax/mcp-serverClaude Desktop / Cursor / Windsurf
Add to your MCP config file:
{
"mcpServers": {
"agenttax": {
"command": "npx",
"args": ["@agenttax/mcp-server"],
"env": {
"AGENTTAX_API_KEY": "atx_live_your_key"
}
}
}
}Demo mode works without a key (10 calls/day, no account required). Tools marked "Yes" below need AGENTTAX_API_KEY.
Tools
Tool | What it does | Key needed |
| Log a payment you received and get your sales tax liability. The main tool for paid MCP servers and APIs. | Demo works; key for history |
| Sales/use tax calculation. Keyless: an estimate (total, rates, confidence, | Demo works (estimate); key for full response |
| Bulk-log up to 100 transactions (e.g. x402 purchases), idempotent on | Yes |
| Your transaction history with running totals | Yes |
| Each state's economic nexus thresholds (revenue / transaction count), notes and DOR source | No |
| The states you have configured nexus in | Yes |
| Set the states you have nexus in (merge semantics) | Yes |
| Log a buy/sell; sells return realized gain/loss with cost basis | Yes |
| Trades you have logged | Yes |
| Draft Form 1099-DA payload for realized digital-asset gains | Yes (Pro) |
| State sales tax rates and digital-goods taxability, all 51 jurisdictions or one | No |
| Combined state + local rate for a zip code | No |
| State short/long-term capital gains rates | No |
| Machine-readable pricing contract | No |
| API health and endpoint list | No |
Read-only tools carry the MCP readOnlyHint annotation so clients can auto-approve them.
track_payment
track_payment({
amount: 49.00,
buyer_state: "TX",
buyer_zip: "78701",
description: "MCP tool subscription",
work_type: "content",
payment_id: "pi_stripe_abc123",
source: "stripe"
})Returns tax_owed, tax_rate, taxable, transaction_id, a classification (where the work type came from) and a compliance_note. Sellers get $0 in states where no nexus is configured. That $0 is a default, not a determination, and the response says so: nexus_status (unknown / no_nexus_profile), tax_if_nexus (what the payment owes once nexus is set), nexus_warning (the API's NEXUS_NOT_CONFIGURED advisory or demo note) and a compliance_note such as "No sales tax collected because no nexus is configured for WA ... If you have nexus in WA, this payment owes $6.50 (6.5%)." Keyless calls use AgentTax's shared demo nexus profile, not yours.
Pass work_type explicitly (compute | research | information_service | content | consulting | trading | payment_processing | web_hosting | software_maintenance | it_support | custom_software) when you know what you sold. The last five are the classification work types the API added in October 2026: a payment or facilitator fee, hosting the buyer's own site, a software maintenance contract, IT support, and software written for one buyer. Each sends its own transaction_type and the API answers with that state's rule for it. It is a declaration and gives the exact answer, and it is the only way the consulting or trading exemption applies: for example, AI consulting sold to an Arizona buyer is an exempt professional service (A.R.S. §42-5061(A)(1), TPR 93-48), so work_type: "consulting" returns $0 in AZ. Without work_type the server guesses from description, but a guess never takes the consulting or trading exemption: a description that looks like consulting (e.g. "SOC 2 audit platform subscription") or trading is taxed as SaaS, and classification.note tells you to resend with work_type if the guess was right. A description that looks like compute or research keeps the 1.1.1 classification, which can tax less than SaaS in some states (e.g. CT, MD, SC, TN, WV); pass work_type for an exact answer. Leave is_b2b out when you don't know the buyer; false declares a consumer. Upgrading from 1.1.1? Some track_payment results change; see CHANGELOG.md.
calculate_tax
calculate_tax({
role: "buyer",
amount: 500,
buyer_state: "TX",
buyer_zip: "78701",
transaction_type: "compute",
work_type: "compute",
counterparty_id: "seller-agent-123",
is_b2b: true
})Optional fields: seller_state / seller_zip (origin-sourced intrastate sales in TX, UT, AZ, TN and some OH sales), use_context (Maryland B2B), digital_content_type (with transaction_type: "digital_good"), seller_remitting. transaction_type and work_type are sent exactly as given and treated as declared facts; don't guess them (consulting is exempt in Arizona).
Classification facts (optional; sent to the API as given, except that payment_provider_type and it_support_scope are trimmed and lowercased first, as the API does). Each one applies to one of the classification types; leave it out and the API gives its conservative default for that type.
payment_provider_type(bank|licensed_money_transmitter|card_network|processor_routing_to_bank_or_network|other), withtransaction_type: "payment_processing_fee": who provides the payment processing.it_support_scope(help_desk_advice|remote_repair_or_config|software_installation|monitoring|security_monitoring|managed_bundle), withit_support: what the engagement is. Absent meansmanaged_bundle.includes_prewritten_software_access(boolean), withtransaction_type: "web_hosting":truewhen the plan gives the buyer vendor software beyond an incidental control panel or file manager (site builder, CMS or app platform, email or office suite, managed application).custom_software_attestation, required withwork_type: "custom_software"; without a complete one the sale is answered as prewritten software / SaaS. Required keys:written_for_buyer,not_offered_to_others,deliverable(source_code|compiled_artifact|hosted),is_modification_of_prewritten. Optional state facts:separately_stated_charge,all_rights_transferred,delivery(electronic|tangible),il_requirements_analysis_and_adaptation,il_assembled_modules_50pct.maintenance_contract, withtransaction_type: "software_maintenance". All keys optional:mandatory,includes_upgrades,includes_support,separately_itemized,itemized_amounts({ updates, support }, summing toamount),update_delivery(electronic|tangible),support_kind(help_desk_only|includes_fixes),seller_sold_software,business_use.
Both objects are strict, as in the API: an unknown key is refused before the call is sent. The facts are your representation and are recorded with the transaction. track_payment does not take them; use calculate_tax when you have them. ingest_transactions records take the same facts per record and pass them through to the API, which validates them; leave them out and an ingested classification sale gets the conservative answer.
calculate_tax({
role: "seller", amount: 12000, buyer_state: "TX", counterparty_id: "client-42",
transaction_type: "saas", work_type: "custom_software",
custom_software_attestation: {
written_for_buyer: true, not_offered_to_others: true,
deliverable: "source_code", is_modification_of_prewritten: false
}
})intent (optional, "estimate" | "record"). Pass "estimate" to quote a price before a wallet signs. An estimate is computed and counts toward your monthly quota, but it is never saved to your transaction history, never counts toward nexus revenue, and ignores any idempotency key. With an API key and no intent, the call is a "record" and is logged. Keyless demo calls are always estimates. The server sends intent only when you pass it. It needs the AgentTax API release that accepts intent (live on agenttax.io since 2026-10-21).
resolution in the response says how sure each part of the answer is. resolution.location, resolution.nexus and resolution.taxability each carry a status (resolved, partial or unknown), a basis (for example zip_local_rate, state_only, no_nexus_profile, fact_not_declared) and a detail sentence. total_tax is always returned, never withheld. If your rule is "unknown means do not charge", branch on the status yourself:
// Pseudo-code. quote = the parsed JSON result of the calculate_tax tool call
const price = 20;
const quote = await calculate_tax({
role: "seller", amount: price, buyer_state: "NY", buyer_zip: "10001",
transaction_type: "saas", counterparty_id: "buyer-agent-7", intent: "estimate"
});
if (quote.resolution.nexus.status === "unknown") {
// No nexus profile configured: total_tax may be $0 only because nexus was never set up.
// Run configure_nexus, or hold the sale for review, instead of charging $0.
} else {
charge(price + quote.total_tax);
}Nexus
get_nexus_thresholds({ state: "NY" }) // what triggers registration
configure_nexus({ nexus: { TX: { hasNexus: true, reason: "Economic nexus" } } })
get_nexus() // what you have configuredCapital gains and 1099-DA
log_trade({ asset_symbol: "ETH", trade_type: "buy", quantity: 2, price_per_unit: 2500, asset_class: "crypto" })
log_trade({ asset_symbol: "ETH", trade_type: "sell", quantity: 1, price_per_unit: 3100, asset_class: "crypto" })
export_1099_da({ year: 2026 }) // draft, not a filed returnGet an API Key
curl -X POST https://agenttax.io/api/v1/auth/signup \
-H "Content-Type: application/json" \
-d '{"email": "you@example.com", "password": "securepass", "agent_name": "my-mcp-server", "agent_work_type": "compute"}'All four fields are required; agent_work_type is one of compute, research, information_service, content, consulting, trading, payment_processing, web_hosting, software_maintenance, it_support, custom_software. Save the api_key.key from the response — it's only shown once.
Pricing
Tier | Price | Calls/month |
Free | $0 | 1,500 |
Starter | $25/mo | 10,000 |
Growth | $99/mo | 100,000 |
Pro | $199/mo | 1,000,000 |
x402 | $0.005/call in USDC on Base | Pay per call, no signup |
Current machine-readable pricing: get_pricing or GET https://agenttax.io/api/v1/pricing.
Links
License
MIT
Available Tools
6 toolscalculate_taxB
Calculate US sales tax or use tax for an AI agent transaction. Returns tax amount, rate, jurisdiction, audit trail, and advisories.
Inputs: role (required), amount (required), buyer_state (required), counterparty_id (required), +5 more.
check_healthB
Check AgentTax API health, available endpoints, pricing tiers, and registry validation status.
Inputs: no named parameters.
configure_nexusA
Configure which US states you have economic nexus in. Sellers must configure nexus to get non-zero tax results. Requires API key.
Inputs: nexus (required).
get_ratesA
Get US sales tax rates. Returns rate, digital taxability, SaaS notes, and verification metadata for all 51 jurisdictions or a single state.
Inputs: state, format, explain.
log_tradeA
Log a buy or sell trade for capital gains tracking. Sell trades return realized gain/loss with cost basis.
Inputs: quantity (required), trade_type (required), asset_symbol (required), price_per_unit (required), +4 more.
track_paymentA
Track a payment you received and calculate your sales tax liability. Call this after receiving any payment — Stripe, x402, or direct. Automatically classifies the transaction, calculates tax owed, and logs it to your AgentTax account.
Inputs: amount (required), buyer_state (required), is_b2b, source, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Most tools target distinct concerns: get_rates fetches rates, configure_nexus sets state configuration, check_health reports status, and log_trade handles capital gains. However, track_payment and calculate_tax overlap significantly, since track_payment also calculates tax owed, making it unclear when an agent should use one versus the other.
All six tools follow a clean verb_noun snake_case pattern: track_payment, calculate_tax, get_rates, configure_nexus, check_health, log_trade. The convention is fully predictable and readable.
Six tools is well-scoped for a niche tax/accounting server. Each tool covers a distinct lifecycle step (configure, fetch rates, calculate, track, log, health-check) without bloat.
The surface covers configuration, calculation, and logging, but there is no way to retrieve or list previously logged payments or trades, and no update/delete or reporting/filing operations. Logging without a corresponding read-back creates a notable dead end for agents.
Maintenance
Related MCP Connectors
Merchant-of-record MCP: AI agents sell software & digital goods, global tax handled, BYO key.
Agent Commerce Protocol MCP — bridges Stripe ACP + Google AP2 + Coinbase x402 for agent payments
Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.
Real-time US and Canadian sales and use tax rates by address or geo coordinates.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables MCP hosts like Claude, VS Code, Cursor, and others to discover payment methods, create payment links, verify payments, inspect invoices, and manage refunds through focused tools, with a guided safe payment workflow and a restricted generic API escape hatch.735 npmMIT
- AlicenseAqualityBmaintenanceMerchant of record MCP server: create products, payment links, checkouts, subscriptions, invoices and discount codes, with VAT and sales tax handled in 135+ jurisdictions.3112 npm8Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents and MCP hosts to add stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based access logic to applications.-
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to manage Agentic Payment Protocol ephemeral tokens with cryptographic spend mandates, risk scoring, merchant catalog resolution, and automated bargaining through MCP tools.MIT