Use Tax MCP from Claude or ChatGPT
A hosted ChatGPT/Claude one-click connector is not yet generally available. What works today is a connection you configure yourself with your own API key: an MCP client for Claude, or a Custom GPT Action for ChatGPT.
Before you connect an assistant
Do not paste taxpayer facts into a generic chatbot unless your integration is configured to call Tax MCP through an authenticated, logged, policy-compliant tool path — anything you type into an assistant is processed by that assistant's provider before a tool call ever reaches Tax MCP.
Claude: connect an MCP client
Tax MCP serves the Model Context Protocol over Streamable HTTP at POST https://tax-mcp.com/mcp, with five tools: tax_capabilities, tax_compute_federal, tax_compute_state, tax_compute_return_lines, and tax_compute_efile_readiness. It authenticates with the same Authorization: Bearer key, checked before the MCP handshake.
Create a dedicated key
Use a dedicated, revocable key for each assistant (see Get an API key), so you can revoke it without touching your production key.
Add the server to a client that can send a header
For Claude Code:
claude mcp add --transport http tax-mcp https://tax-mcp.com/mcp \ --header "Authorization: Bearer YOUR_MCP_API_KEY"Claude Desktop and other MCP clients that accept a remote server URL with a custom Authorization header work the same way. A browser connector flow that requires OAuth will not work with this static-key endpoint.
Ask it to compute
The assistant should call
tax_capabilitiesfirst to learn the fields. A decline comes back as a normal successful tool result (computed: falsewith a reason), not a protocol error, so the assistant should explain it rather than retry.
The /mcp transport is in an eval (non-metered) posture; subject to change. Unlike the REST API, it does not bill, use quota, or accept idempotency keys today; it has a flat abuse ceiling of 60 requests a minute per key. Details: MCP transport reference.
ChatGPT: a Custom GPT Action
These steps reflect the GPT builder as of mid-2026; if a screen looks different, check OpenAI's Actions documentation.
Create a GPT and import the spec
In ChatGPT, create a GPT, open Configure → Actions, and choose Import from URL with
https://tax-mcp.com/api/openapi.json(OpenAPI 3.1).Set authentication
Choose API Key with auth type Bearer, and paste a dedicated, revocable key. Quota is per account, so a leaked key can use up the account's monthly calls until you revoke it.
Keep it private and test
Ask it to compute the quickstart example. A decline in a test is a correct result, not a broken Action.
Calls from a GPT Action go through the normal metered REST API, with the same billing, quota, idempotency, and rate-limit behavior as any other client.
See also: MCP transport and Get an API key.