`fda_adcom_materials`

Pack: regulatory-catalysts · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/fda_adcom_materials for the schema, then POST the same URL with its arguments for the data.

What evidence is an FDA advisory committee reviewing? For one FDA advisory committee (AdCom) meeting — picked by committee (ODAC, VRBPAC, CTGTAC, or any name fragment), by date, and/or by drug, sponsor or topic — returns the meeting page’s posted materials: FDA and sponsor briefing documents, the agenda, questions to the committee, rosters, presentation slides, minutes and transcripts, each with a document type, party (FDA / sponsor / combined), file type and size, and URL. Also extracts the agenda text, the applications under review (NDA/BLA number, product, sponsor, proposed indication), the public docket number, the webcast link, and — when a Questions document is posted — the VOTING QUESTIONS text itself. Reads FDA’s own advisory-committee calendar (fda.gov, keyless), which lists meetings from 2016 to the next scheduled one; when a meeting has nothing posted yet it says so with the meeting date and FDA’s posting timeline instead of returning an empty list. Use for AdCom briefing document, FDA briefing book, advisory committee materials, ODAC questions, what is the panel voting on, sponsor briefing package, panel agenda, FDA presentation slides, AdCom transcript or minutes. Pair with fda_adcom_calendar (which meetings are coming) and pdufa_catalysts (the decision date that follows the panel).

Parameters

Name	Type	Required	Description
`committee`	string	no	Committee acronym or name fragment, case-insensitive: “ODAC”, “VRBPAC”, “CTGTAC”, “oncologic”, “vaccines”, “gene therap”, “cardiovascular”, “psychopharmacologic”, “medical devices”… Omit to search every committee.
`date`	string	no	Meeting date filter: a day “2026-04-30”, a month “2026-04”, or a year “2026”. Omit to pick the meeting nearest to today (upcoming or just past).
`query`	string	no	Drug, sponsor, application or topic to find the meeting by, e.g. “camizestrant”, “AstraZeneca”, “NDA 220359”, “COVID-19 vaccine”. Matched against meeting titles first, then against the agenda text of the nearest candidate meetings.
`limit`	number,string	no	Number of meetings to return with their materials (1–3). Default 1 — the single best match.
`include_questions_text`	boolean,string	no	When a “Questions” document is posted, fetch it and return the voting-question text (default true). Set false to skip the extra PDF fetch.

Example call

Arguments

{
  "committee": "ODAC"
}

curl

curl -X POST https://gateway.pipeworx.io/regulatory-catalysts/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"fda_adcom_materials","arguments":{"committee":"ODAC"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('fda_adcom_materials', {
  "committee": "ODAC"
});

More examples

{
  "committee": "oncologic",
  "date": "2026-04-30"
}

{
  "query": "camizestrant"
}

{
  "committee": "VRBPAC"
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the regulatory-catalysts pack

{
  "mcpServers": {
    "regulatory-catalysts": {
      "url": "https://gateway.pipeworx.io/regulatory-catalysts/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

fda_adcom_materials