Get started

Set up

Everything you need before your first call: an account, a plan, an API key in your environment, and a quick check that the service can see you.

Checklist

  1. Create an account

    Sign in with Google. Your account starts on the Free plan: 250 calls a month, 1 API key, and 10 requests a minute. No card is required.

  2. Pick a plan when you need more

    Plans differ in monthly calls, number of keys, and requests per minute; every plan computes the same coverage. Each plan's limit is a hard cap with no overage charge. Compare them on Pricing and change plans from your dashboard.

  3. Create an API key

    In the dashboard, choose Create API key and copy it immediately; it is shown once. Details, including rotation and revocation, are in Get an API key.

  4. Put the key in your environment

    Every example in these docs reads the key from TAX_MCP_API_KEY:

    Shell
    # Keep the key out of source code and shell history files you share.
    export TAX_MCP_API_KEY="<paste the key from your dashboard>"
  5. Check your tools

    Any HTTPS client works. The examples use curl with uuidgen (for the Idempotency-Key header), and the quickstart also shows TypeScript (Node 18+, built-in fetch) and Python (requests). There is no SDK to install; the OpenAPI 3.1 spec can generate a client if you want one.

  6. Confirm the service and your key

    The capability manifest needs no key and costs nothing. It lists every modeled field, affirmation, and decline code:

    No key needed
    curl https://tax-mcp.com/api/mcp/tax-capabilities -H "Accept: application/json"

    A GET on a compute endpoint checks your key without using quota. A 200 means the key works; a 401 means it is missing, mistyped, or revoked.

    Checks the key, free
    curl https://tax-mcp.com/api/mcp/tax-compute/federal \
      -H "Authorization: Bearer $TAX_MCP_API_KEY"

Use the canonical host

Send every request to https://tax-mcp.com, except document intake, which has its own host. Older proxy paths and service URLs exist only for migration; new integrations should not use them.

Data you send

Send only the facts a computation needs. Never put an API key, a Social Security number, or a taxpayer document in a support email or feedback form. See privacy & sanitization.

See also: Quickstart.