
OpenFDA
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
README
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
-
Set up your OpenFDA API Key
The 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. -
Example MCP Server Configuration
If 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?
git clone https://github.com/ythalorossy/openfda.git
cd openfda
npm install
Usage
First, build the project:
npm run build
Then, start the server from the build folder:
node build/index.js
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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.