FDA Intel

Connect your AI (MCP)

Other MCP clients

Any client that supports remote MCP servers over Streamable HTTP can connect.
  1. 1

    Give your client the address

    Server URL: https://fdaintel.ai/mcp. Transport: Streamable HTTP. Clients that support the MCP authorization spec discover OAuth on their own from the 401 reply.
    Generic config
    {
  "mcpServers": {
    "fda-intel": {
      "type": "http",
      "url": "https://fdaintel.ai/mcp"
    }
  }
}
  2. 2

    Or send an API key

    If the client can't do OAuth, create an API key on your account page and send it as a header.
    With an API key
    {
  "mcpServers": {
    "fda-intel": {
      "type": "http",
      "url": "https://fdaintel.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${FDA_INTEL_API_KEY}"
      }
    }
  }
}
  3. 3

    Local-only clients: use a stdio bridge

    Clients that only start local (stdio) servers can run a bridge that forwards to the remote server with your key, for example npx -y mcp-remote https://fdaintel.ai/mcp --header "Authorization: Bearer $FDA_INTEL_API_KEY".

Discovery and metadata#

Server card
https://fdaintel.ai/.well-known/mcp.json
Protected resource metadata
https://fdaintel.ai/.well-known/oauth-protected-resource/mcp
Authorization server metadata
https://fdaintel.ai/.well-known/oauth-authorization-server
Dynamic client registration
POST https://fdaintel.ai/oauth/register

Agent frameworks#

Frameworks with an MCP client (OpenAI Agents SDK, the Anthropic API MCP connector, LangChain MCP adapters and others) take the same URL and an Authorization header with your API key.

Something not working?

See the FAQ, or email us with the time and the client you used. Never send your API key.