OpenFDA

OpenFDA MCP Server

A Model Context Protocol (MCP) server for querying drug information from the OpenFDA API.

Features

• Retrieve drug label information by brand name
• Retrieve drug information by generic (active ingredient) name
• Get all brand versions of a generic drug
• Get adverse event (side effect) reports for a drug (by brand or generic name)
• Retrieve all drugs manufactured by a specific company
• Get comprehensive drug safety information (warnings, contraindications, interactions, precautions, etc.)
• Normalize and validate NDC (National Drug Code) formats
• Helpful error messages and suggestions for failed queries

1. Set up your OpenFDA API KeyThe MCP server requires an OpenFDA API key to access the OpenFDA API.
   Create a .env file in the root of your project and add the following line:
   OPENFDA_API_KEY=your_openfda_api_key_here

   Note: Never commit your real API key to version control.
   You can obtain an API key from OpenFDA API Key Registration.

2. Example MCP Server ConfigurationIf you are integrating this server with a larger MCP system, your configuration might look like:
   { "mcpServers": { "openfda": { "command": "npx", "args": ["@ythalorossy/openfda"], "env": { "OPENFDA_API_KEY": "************" }, "timeout": 60000 } } }
   Replace the asterisks with your actual API key, or ensure it is loaded from your .env file.

Want to run it local?

Usage

First, build the project:

Then, start the server from the build folder:

Key Points:

• The build step (npm run build) compiles your source files into the build/ directory.
• You should run the compiled output (e.g., build/bin/index.js), not the source file (bin/index.js), unless your project is set up to run directly from source.

Configuration

Create a .env file for any required environment variables.

License

MIT

Buy me a Coffee