MCP connector

Connect Tandom customs tools to Claude, Codex, ChatGPT, and Cursor.

Tandom exposes a remote MCP endpoint for AI agents that need customs intelligence during a workflow. Give the agent a Tandom API key, point it at the endpoint, and ask from the operator's point of view.

Get an API keyView agent workflows

Endpoint

https://mcp.tandom.ai/mcp

Transport: Streamable HTTP. Authentication today: Authorization: Bearer with a Tandom API key. Directory clients use OAuth discovery, dynamic client registration, and PKCE authorization.

Works today

Codex CLI, Cursor, Anthropic Messages API, OpenAI Responses API, and any MCP client that can send a bearer token.

Directory path

OAuth metadata, dynamic client registration, PKCE authorization, and token exchange are the connector-review path. Platform approval still requires submission.

Tool policy

Only read-only, available-now customs tools are listed. Closed-beta and write-like workflows stay out of the connector until review gates are ready.

For everyone

Add Tandom to the AI assistant you already use

Pick your assistant. Each setup takes about a minute and only needs a Tandom account — no API keys, no terminal commands.

Claude

Works today

Use Tandom inside Claude.ai (web) or the Claude desktop app. OAuth handles sign-in — no API keys to paste.

Claude's Add custom connector dialog with the Tandom MCP URL filled in.
  1. 1.Open Claude. Click your profile (bottom left) → Settings → Connectors.
  2. 2.Scroll to the bottom of the connector list and click Add custom connector.
  3. 3.Name: Tandom. Remote MCP server URL: https://mcp.tandom.ai/mcp. Click Add.
  4. 4.Click Connect on the new Tandom row.
  5. 5.Sign in to your tandom.ai account when redirected, then click Allow on the Tandom consent page.
  6. 6.You return to Claude with Tandom now showing Connected.

Tip — Once-per-install: Settings → Connectors → Tandom → Configure → Blanket permission for group → Always allow. All Tandom tools are marked read-only, so this only skips per-call approval prompts.

ChatGPT

Works today

Use Tandom inside chatgpt.com on Plus, Pro, or Enterprise. ChatGPT installs custom MCP apps with OAuth — no keys to paste.

ChatGPT's Add a custom MCP form with the Tandom URL filled in.
  1. 1.Open ChatGPT. Click your profile → Settings → Connectors → Advanced. (Or open Apps and click Manage.)
  2. 2.Click Add a custom MCP.
  3. 3.Name: Tandom. URL: https://mcp.tandom.ai/mcp. Auth: OAuth (default).
  4. 4.Check the 'I understand' acknowledgement and click Create.
  5. 5.Sign in to your tandom.ai account when redirected, then click Allow on the Tandom consent page.
  6. 6.Tandom appears under Enabled apps with a DEV badge — that's the standard label for any MCP server that's not yet OpenAI-reviewed.

Tip — Once-per-install: Settings → Apps → Tandom → set tool access to Always allow for read-only tools.

Google Gemini

Works today via AI Studio

Native MCP install in vanilla gemini.google.com isn't generally available yet. The supported path today is Google AI Studio, which accepts custom MCP server URLs and uses the same Google account.

  1. 1.Open aistudio.google.com and sign in with your Google account.
  2. 2.Create a new prompt or open an existing one.
  3. 3.In the right panel, switch to the Tools tab.
  4. 4.Click + Add tool → Custom MCP server.
  5. 5.Name: Tandom. URL: https://mcp.tandom.ai/mcp. Auth: OAuth.
  6. 6.Sign in to your tandom.ai account when redirected, then click Allow on the Tandom consent page.

Tip — Vertex AI Agent Builder users can register Tandom under Tools → Custom MCP server the same way. We'll surface a native vanilla-Gemini install path here once Google ships it.

Building with the API

Programmatic clients and IDE setups

For developers wiring Tandom into Codex, Cursor, Claude Code, or the Anthropic and OpenAI APIs directly. Uses Tandom API keys instead of interactive OAuth.

Codex CLI / Codex IDE

Works today

Codex supports streamable HTTP MCP servers and can read a bearer token from an environment variable.

export TANDOM_API_KEY="tk_live_..."
codex mcp add tandom \
  --url https://mcp.tandom.ai/mcp \
  --bearer-token-env-var TANDOM_API_KEY

codex mcp list

Cursor

Works today

Cursor supports remote MCP servers and header interpolation from environment variables in mcp.json.

{
  "mcpServers": {
    "tandom": {
      "url": "https://mcp.tandom.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${env:TANDOM_API_KEY}"
      }
    }
  }
}

Claude Messages API

Works today

Claude's MCP connector can call a remote MCP server directly from a Messages API request with an authorization token.

curl https://api.anthropic.com/v1/messages \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $ANTHROPIC_API_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "anthropic-beta: mcp-client-2025-11-20" \
  -d '{
    "model": "claude-sonnet-4-20250514",
    "max_tokens": 1200,
    "messages": [{
      "role": "user",
      "content": "Use Tandom to check duties and AD/CVD risk for stainless steel forged flanges from China."
    }],
    "mcp_servers": [{
      "type": "url",
      "name": "tandom",
      "url": "https://mcp.tandom.ai/mcp",
      "authorization_token": "tk_live_..."
    }]
  }'

OpenAI Responses API

Works today

The Responses API can attach a remote MCP server with headers. Use this path for programmatic OpenAI tests before ChatGPT directory submission.

curl https://api.openai.com/v1/responses \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -d '{
    "model": "gpt-5",
    "input": "Use Tandom to check HTS, duty, PGA, and AD/CVD risk for a broker entry line.",
    "tools": [{
      "type": "mcp",
      "server_label": "tandom",
      "server_url": "https://mcp.tandom.ai/mcp",
      "headers": {
        "Authorization": "Bearer tk_live_..."
      },
      "require_approval": "never"
    }]
  }'

Claude Code

OAuth review path

Claude Code supports remote HTTP MCP servers. For remote auth, use the OAuth flow in /mcp once Tandom OAuth is live.

claude mcp add --transport http tandom https://mcp.tandom.ai/mcp

# Inside Claude Code:
> /mcp

# Then authenticate the Tandom server once OAuth is enabled.

Available tools

The authenticated connector lists read-only customs tools.

These mirror available-now API endpoints. Report generation, classification, forms, quote orchestration, monitoring, and other closed-beta workflows stay out of the public connector until their product and review contracts are ready.

  • tandom_duty_calculate
  • tandom_pga_check
  • tandom_chapter99_applicable
  • tandom_hts_search
  • tandom_hts_notes
  • tandom_hts_hierarchy
  • tandom_adcvd_check
  • tandom_adcvd_orders_search
  • tandom_regulatory_status

Prompt to try

I am a customs broker preparing an entry line.
Use Tandom to check HTS context, duty stack, PGA requirements, and AD/CVD risk.

Product: stainless steel forged flanges
HTS hint: 7307.91.50.10
Origin: China
Customs value: 10000
Entry date: 2026-04-30

Return the tool calls, assumptions, citations, and any missing facts.

References

Treat MCP clients as separate trust boundaries. Tandom tools are read-only today, but agents may still send product descriptions, HTS hints, supplier names, or shipment facts as tool arguments.