Skip to main content
Glama
AgentTax

AgentTax MCP Server

Official
by AgentTax

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENTTAX_API_KEYNoYour AgentTax API key. Demo mode works without a key (50 calls/day).

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
calculate_taxB

Calculate US sales tax or use tax for an AI agent transaction. Returns tax amount, rate, jurisdiction, audit trail, and advisories.

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.

log_tradeA

Log a buy or sell trade for capital gains tracking. Sell trades return realized gain/loss with cost basis.

get_ratesA

Get US sales tax rates. Returns rate, digital taxability, SaaS notes, and verification metadata for all 51 jurisdictions or a single state.

configure_nexusA

Configure which US states you have economic nexus in. Sellers must configure nexus to get non-zero tax results. Requires API key.

check_healthB

Check AgentTax API health, available endpoints, pricing tiers, and registry validation status.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 6 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness3/5

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

ActivityInactive
ResponsivenessUnresponsive