Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@FastMCP Server Templateshow me how to add a new tool to the server"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
FDA MCP Server
An MCP (Model Context Protocol) server that provides FDA medical device verification capabilities for prior authorization workflows. Queries the FDA 510(k) database to verify device clearance status and make PA approval decisions.
Features
Device Search: Search FDA 510(k) database by K-number, device name, manufacturer, or product code
Fuzzy Matching: Intelligent fuzzy search with confidence scoring when exact identifiers aren't available
PA Verification: Analyze FDA search results and make prior authorization approval decisions
Confidence Scoring: Each result includes confidence scores based on match quality
OpenShift Deployment: Production-ready deployment to Red Hat OpenShift
Tools
search_fda_device
Unified FDA search tool that accepts any combination of identifiers or descriptive information.
Parameters:
device_identifiers(optional): FDA identifiers (k_number, pma_number, product_code, udi)device_description(optional): Device info for fuzzy search (device_name, manufacturer)search_options(optional): Search options (fuzzy_search, max_results)
Search Strategies (in priority order):
K-number exact match (confidence: 1.0)
Product code + fuzzy name (confidence: 0.75-0.9)
Fuzzy name/manufacturer search (confidence: 0.5-0.6)
Example:
verify_fda_approval
Analyze FDA search results and make PA approval decision with structured reasoning.
Parameters:
fda_search_results: Results fromsearch_fda_devicetoolpa_requirements(optional): PA requirements (required_device_class, require_otc, require_cleared_or_approved)
Returns:
Approval decision (approve/deny)
Requirements check details
Human-readable reasoning
Action items for next steps
Example:
Quick Start
Local Development
Deploy to OpenShift
Product Codes Reference
Common FDA product codes for hearing devices:
Code | Description |
QUH | OTC Self-Fitting Air-Conduction Hearing Aid |
OSM | Prescription Hearing Aid |
LYY | Cochlear Implant System |
Response Schema
All tools return structured responses:
Environment Variables
MCP_TRANSPORT- Transport type (stdio/http)MCP_HTTP_HOST- HTTP host (default: 0.0.0.0)MCP_HTTP_PORT- HTTP port (default: 8080)MCP_HTTP_PATH- HTTP endpoint path (default: /mcp/)
Related Projects
pa-workflow-simple - Prior authorization workflow system that uses this MCP server
fhir-mcp - FHIR patient data MCP server
License
MIT License - see LICENSE for details.