openFDA MCP integration
Public FDA drug labels, adverse events, drug recalls, and medical device recall data.
Sign in and add openFDA in Apps. No openFDA account is required.
Tools
| Name | Description |
|---|---|
search_drug_labelsSearch public FDA structured product labels. Use targeted search terms; this endpoint does not contain patient PHI. | Search public FDA structured product labels. Use targeted search terms; this endpoint does not contain patient PHI. |
search_drug_adverse_eventsSearch public FAERS drug adverse event reports by precise openFDA query. | Search public FAERS drug adverse event reports by precise openFDA query. |
search_drug_recallsSearch FDA drug enforcement/recall reports by recall number, firm, product, classification, or date query. | Search FDA drug enforcement/recall reports by recall number, firm, product, classification, or date query. |
search_device_recallsSearch FDA medical device enforcement reports by precise openFDA query. | Search FDA medical device enforcement reports by precise openFDA query. |
Quick Start
import { WeavzClient } from '@weavz-io/sdk'
const weavz = new WeavzClient({ apiKey: 'wvz_...' })
const result = await weavz.actions.execute('openfda', 'search_drug_labels', {
workspaceId: '550e8400-e29b-41d4-a716-446655440000',
integrationAlias: 'openfda',
input: { /* ... */ },
})Related Integrations
Works well with
Frequently Asked Questions
Is there a openFDA MCP server through Weavz?
Yes. Add the openFDA integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 4 openFDA actions.
What can an AI agent do with openFDA?
Available actions include Search Drug Labels, Search Drug Adverse Events, Search Drug Recalls, Search Device Recalls. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.
How do I connect openFDA to Claude or ChatGPT?
Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add openFDA, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.
Can I use openFDA through an API or SDK?
Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.
What authentication does openFDA require?
This catalog integration does not require a stored external account connection. Provider terms, rate limits and tool-specific inputs can still apply.
How do I review sensitive openFDA actions?
Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.
What limits or costs apply to openFDA?
Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.
Connect openFDA in minutes
Get 20,000 free action executions every month. No credit card required.