ChatGPT and Claude integrations

Use Tariff Code Compliance with ChatGPT and Claude

Use Tariff Code Compliance from ChatGPT or Claude to research product classifications against the current TCC tariff knowledge graph. These integrations are available today through private/custom connections. They have not been approved for public listing in the OpenAI Plugins Directory or an Anthropic directory.

How the integration works

ChatGPT or Claude discovers the tariff systems and exact versions available at runtime, asks for missing product facts, researches candidate nodes and their relationships, and returns a structured, session-local recommendation. A complete result identifies the selected system and version, recommended code, supporting evidence, rejected alternatives, assumptions, and uncertainty. If the material facts are insufficient, it returns unresolved candidates and focused follow-up questions instead of forcing a code.

Agent results are research support. They are not legal advice, a binding customs ruling, a saved TCC proposal, or an automatic write to another system.

Before connecting

  • You need a ChatGPT plan that supports developer-mode apps or a Claude plan that supports custom connectors.
  • Use the production MCP URL exactly as shown: https://api.prod.tariffcodecompliance.com/tariff-code-compliance/v1/mcp.
  • You will sign up or sign in with Auth0 and approve access to the TCC knowledge graph.
  • New accounts currently receive the internal explorer-beta-free plan. Accepted MCP calls produce usage records. That beta plan does not currently charge or enforce a customer usage limit, but TCC may use these records for usage-based pricing, limits, or enforcement under a future or different plan and applicable terms.

Connect from ChatGPT

Current private setup uses ChatGPT developer mode; this is not a claim of public directory approval.

  1. Open ChatGPT settings and enable developer mode for apps.
  2. Create a private app/plugin connection using the production MCP URL above.
  3. Start the connection. ChatGPT follows the protected-resource metadata to Auth0.
  4. Sign up or sign in, review the requested tcc.knowledge_graph.read scope, and approve consent.
  5. Ask ChatGPT to list the available tariff systems before the first classification.

OpenAI now uses one Plugins Directory shared by ChatGPT and Codex. Public availability requires OpenAI review and a later publisher action; TCC has not completed those steps.

Connect from Claude

  1. Open Customize, then Connectors.
  2. For an individual account, add a custom connector with the production MCP URL. For Team or Enterprise, an owner must first add the organization connector.
  3. Choose Connect. Claude opens the Auth0 OAuth sign-up/sign-in and consent flow.
  4. After consent, ask Claude to list the available tariff systems before the first classification.

The connector uses OAuth and Streamable HTTP. Do not paste access tokens or credentials into chat or connector configuration fields other than the normal Auth0 sign-in screen.

A good first request

Try: Classify a men's knitted cotton T-shirt for import into the United States. Ask me for any facts you still need and show rejected alternatives.

For the best result, include the destination, principal function, materials or composition, construction, intended use, and whether the item is a complete product, part, set, or kit. Share only facts needed for classification.

Privacy and telemetry

Your AI platform controls the conversation. TCC receives only the inputs that the client selects and sends in MCP tool calls; TCC does not automatically receive the full chat or full product description. Selected text used as a search or lookup input is processed by TCC to return the requested knowledge-graph result.

TCC records reasonable service-interaction context for product analytics, operations, security, support, customer success, sales, and permitted first-party business communications. Depending on how you use the integration, that context may include full page and referrer URLs, searches, product and classification inputs, tariff systems and versions, codes, graph identifiers, tool inputs and results, account/request identifiers, client/protocol details, outcomes, duration, and usage tier. Google Analytics and Vercel Analytics may receive full URL, referral, search, classification, destination, campaign, and custom-event properties configured by TCC. Access-restricted MCP operational logs are generally retained for no more than 90 days. Accepted tool calls also create usage records in Metronome. Those records are non-charging under the current beta plan and may support usage-based pricing, limits, or enforcement under another plan or revised terms.

TCC's classification tools are designed for business product and tariff information, not personal information. Do not send personal information, credentials, authentication secrets, or unrelated data to TCC.

See the Privacy Policy for the full boundary.

Security and revocation

  • TCC uses Auth0 OAuth with authorization code and PKCE. Do not share bearer tokens.
  • Review the requested scope before consenting.
  • Disconnect or remove the custom app/connector in ChatGPT or Claude to stop that client from using TCC.
  • You may also contact TCC support to request account help or deletion. Revoking a client does not erase operational records that TCC must retain for security, reliability, or legal obligations.

Troubleshooting

  • The connection does not open Auth0: confirm the MCP URL is exact and that the client supports remote Streamable HTTP OAuth connectors.
  • Consent or sign-in loops: remove the connection, retry in a normal browser session, and make sure pop-ups are allowed for the client and Auth0.
  • Access denied after sign-in: reconnect so the client can request the current scope and entitlement. If it persists, contact support without sending tokens.
  • A search is too broad: add a specific HTS prefix or related tariff term. The agent should narrow the query rather than repeat it unchanged.
  • The answer says facts are missing: answer the focused follow-up questions. This is an intentional safety outcome, not an error.
  • A result looks incomplete: identify the tariff system/version shown in the answer and contact support. Do not include credentials or the full private conversation.

Technical documentation

See the MCP server documentation for the endpoint, protocol, tool list, and native graph examples. The canonical Markdown for this page is available at /docs/agent.md.