<aside> 🧭

Classify a product for US export control from inside your AI assistant. Describe the product, answer a few questions, and BITE checks it against the International Traffic in Arms Regulations (ITAR) and the EAR Commerce Control List (CCL). You get the classification, whether a license is required, whether you need to file Electronic Export Information (EEI), and where to file.

Works in Claude AI, Claude Code, ChatGPT, Cursor, VS Code and any MCP client that supports remote servers with OAuth.

</aside>

What you can do

<aside> 🔎

Classify a product

Get the ECCN or USML category, jurisdiction and confidence for each check.

</aside>

<aside> 📄

Check license needs

See whether a license is required, why, and which license exceptions may apply.

</aside>

<aside> 🚢

Plan the filing

Find out whether EEI is required, the basis and citation, and where to file.

</aside>

Before you start

Requirement Details
BITE account Sign up at app.bitedata.io.
BITE plan Membership of a team on the Business plan. Teams on a free trial can run one full classification.
AI client A client that supports remote MCP servers (Streamable HTTP) with OAuth sign-in. See Supported clients below.

If you don't have a team yet, BITE prompts you to create one at app.bitedata.io the first time you use the server.

Connection details

Every client uses the same server. Keep these values handy; the setup steps below show where each one goes.

<aside> 🔌

Server URL: https://prod.bitepyapi.com/mcp/gateway

Transport: Streamable HTTP (remote)

Authentication: OAuth 2.0 with PKCE

OAuth Client ID: bite-mcp-gateway (only if your client asks for one)

</aside>

You always sign in on BITE's own sign-in page. Your AI client never sees your BITE password.

Supported clients

Client How to connect Status
Claude (web, desktop, mobile) Connector directory, or Add custom connector ● Supported
Claude Code claude mcp add command ● Supported
ChatGPT Custom connector in Developer mode ● Not verified
Cursor mcp.json ● Not verified
VS Code (GitHub Copilot) .vscode/mcp.json ● Not verified
Codex CLI, Gemini CLI, Windsurf and others Remote MCP server config with the Connection details above ● Not verified

Set up

Claude

  1. In Claude, open Settings → Connectors.
  2. Find BITE Data MCP in the connector directory and select Connect.
  3. Sign in with your BITE account when prompted, and approve access.

<aside> 🏢

On Claude Team and Enterprise plans, an organization owner may need to enable the connector for your workspace first.

</aside>

To add it manually instead, choose Add custom connector and enter:

Claude Code

Run this in your terminal:

claude mcp add --transport http bite <https://prod.bitepyapi.com/mcp/gateway>

Then start Claude Code, run /mcp, select bite and choose Authenticate to sign in with BITE.

ChatGPT

<aside> ⚠️

Custom connectors in ChatGPT require Developer mode and an eligible plan. Menu names change often.

</aside>

  1. Open Settings → Apps & Connectors → Advanced settings and turn on Developer mode.
  2. Select Create, name it BITE, and enter the server URL https://prod.bitepyapi.com/mcp/gateway.
  3. Set authentication to OAuth, then sign in with BITE when prompted.

Cursor

Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "bite": {
      "url": "<https://prod.bitepyapi.com/mcp/gateway>"
    }
  }
}

Open Cursor Settings → MCP, then select Login next to bite to sign in.

VS Code

Add this to .vscode/mcp.json in your workspace, or run MCP: Add Server from the Command Palette:

{
  "servers": {
    "bite": {
      "type": "http",
      "url": "<https://prod.bitepyapi.com/mcp/gateway>"
    }
  }
}

Select Start above the server entry and sign in with BITE when prompted. If VS Code asks for a client ID, enter bite-mcp-gateway.

Other clients

Any client that supports remote MCP servers with OAuth can connect. Use the Connection details above. Common config formats:

Client Where Key for the URL
Codex CLI ~/.codex/config.toml under [mcp_servers.bite] url
Gemini CLI ~/.gemini/settings.json under mcpServers.bite httpUrl
Windsurf ~/.codeium/windsurf/mcp_config.json under mcpServers.bite serverUrl

If your client only supports local (stdio) servers, a bridge such as mcp-remote can connect it to the remote server.

Using it

Ask in plain language. For example:

"Classify a handheld thermal imaging camera with a 640×480 sensor that we're shipping to a distributor in Germany. Does it need an export license?"

"Which of my BITE teams can I use to run an export classification?"