Add the server
Choose OAuth in a supported hosted client, or supply an API key in your own tools.
Bring collected FCC equipment metadata into your AI workflow. Start on Free with 50 API units a month.
Choose OAuth in a supported hosted client, or supply an API key in your own tools.
“Search for this FCC ID and show me the collected application details.”
Check source links, observation times, and collection gaps before drawing conclusions.
https://api.fccidapi.com/mcp
Choose Streamable HTTP. You don’t need to paste an API key when using OAuth.
Add a custom MCP server and choose OAuth. Use the published client identity when offered; leave manually entered client credentials blank.
Check that the consent screen’s return hostname is chatgpt.com.
Add a custom web connector with OAuth sign-in. Leave the client ID and secret blank for automatic setup.
Check that the consent screen’s return hostname is claude.ai.
Add a custom connector and select OAuth. Grok and the xAI console use the same FCC ID API server.
Check that the consent screen’s return hostname is grok.com or console.x.ai.
Ask Muse to add this MCP server using OAuth. Automatic registration is supported. For manual setup, use client ID fccidapi-muse with no secret.
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.
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.
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.
| Tool | Use it to |
|---|---|
search_fcc | Search collected application metadata with a query and page cursor. |
lookup_fcc_id | Look up an FCC ID and inspect match evidence. |
get_application | Read 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.
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.