Your assistant. Our FCC data.

Connect. Ask. Inspect.

Bring collected FCC equipment metadata into your AI workflow. Start on Free with 50 API units a month.

01 / Connect

Add the server

Choose OAuth in a supported hosted client, or supply an API key in your own tools.

02 / Ask

Start with a device

“Search for this FCC ID and show me the collected application details.”

03 / Inspect

Follow the evidence

Check source links, observation times, and collection gaps before drawing conclusions.

One server URL

https://api.fccidapi.com/mcp

Choose Streamable HTTP. You don’t need to paste an API key when using OAuth.

ChatGPT

Add a custom MCP server and choose OAuth. Use the published client identity when offered; leave manually entered client credentials blank.

  1. Enter the server URL above.
  2. Sign in to FCC ID API with your email code.
  3. Check your workspace and requested read access, then choose Allow read access.
  4. Return to chatgpt.com, enable the connection, and ask a question.

Check that the consent screen’s return hostname is chatgpt.com.

Claude

Add a custom web connector with OAuth sign-in. Leave the client ID and secret blank for automatic setup.

  1. Enter the server URL above.
  2. Sign in to FCC ID API with your email code.
  3. Check your workspace and requested read access, then choose Allow read access.
  4. Return to claude.ai, enable the connection, and ask a question.

Check that the consent screen’s return hostname is claude.ai.

Grok

Add a custom connector and select OAuth. Grok and the xAI console use the same FCC ID API server.

  1. Enter the server URL above.
  2. Sign in to FCC ID API with your email code.
  3. Check your workspace and requested read access, then choose Allow read access.
  4. Return to grok.com or console.x.ai, enable the connection, and ask a question.

Check that the consent screen’s return hostname is grok.com or console.x.ai.

Muse

Ask Muse to add this MCP server using OAuth. Automatic registration is supported. For manual setup, use client ID fccidapi-muse with no secret.

  1. Enter the server URL above.
  2. Sign in to FCC ID API with your email code.
  3. Check your workspace and requested read access, then choose Allow read access.
  4. Return to agent.meta.ai, enable the connection, and ask a question.

Check that the consent screen’s return hostname is agent.meta.ai.

Custom connector availability depends on your AI provider’s plan and workspace policy. These are custom connections, not directory listings or endorsements. Grok Bot’s hosted Cursor connection is also supported.

Codex CLI

Create a dedicated key in API keys. SetFCC_API_KEY in the environment where Codex runs, then add the server:

codex mcp add fccidapi --url https://api.fccidapi.com/mcp --bearer-token-env-var FCC_API_KEY

Open a new session and check that the FCC tools are available. SeeCodex’s MCP documentation.

Claude Code

Set FCC_API_KEY in Claude Code’s environment. Merge this server entry into your project’s .mcp.json. Keep the variable reference in the file; do not replace it with a committed key.

{
  "mcpServers": {
    "fccidapi": {
      "type": "http",
      "url": "https://api.fccidapi.com/mcp",
      "headers": {
        "Authorization": "Bearer ${FCC_API_KEY}"
      }
    }
  }
}

Approve the project server when prompted, then use /mcp to check the connection. See Claude Code’s MCP documentation.

What the connection can do

ToolUse it to
search_fccSearch collected application metadata with a query and page cursor.
lookup_fcc_idLook up an FCC ID and inspect match evidence.
get_applicationRead collected technical details and public exhibit locations by source ID.

Successful tool calls use one API unit each. All REST keys and MCP connections share your account’s API allowance. Initialization and tool discovery do not use data units.

You stay in control

OAuth asks for fcc:read. It cannot edit your account, change billing, or manage favorites. Disconnect an app in MCP integration to revoke its access. API-key connections can be revoked from API keys. OAuth access tokens last 15 minutes and rotate through refresh tokens for up to 30 days before reconnection.

Connection troubleshooting
  • No sign-in screen? Confirm the exact /mcp URL and OAuth authentication. Remove stale manually entered credentials.
  • Expired request? Restart setup from your AI app. Consent requests expire after ten minutes.
  • 401 after connecting? Refresh the connection or sign in again. Revoked connections and disabled accounts cannot access data.
  • 429? Check workspace usage. REST and all your assistants share the same allowance.
  • No result? Historical collection is incomplete. A missing record is not an invalidity finding.